On 10/15/2012 19:50, Hans Rosenfeld wrote:
On Mon, Oct 15, 2012 at 05:46:17PM +0200, John Marino wrote:Yes, the warning is correct. That's why it had to be disabled. To avoid a warning with strict-aliasing checking would require recoding. That's a better long-term solution but I'll leave it to the maintainers of libfetch to determine if they want to rewrite the code.If the warning is correct, don't disable it. Disable the optimization feature that triggered it instead. IOW, shouldn't you be using -fno-strict-aliasing here?
Probably. I didn't know the warning was linked with optimization levels. Joerg should probably make the call, he's listed as the maintainer.
John