On Mon, Jul 4, 2016 at 9:47 PM, Marc Lehmann <[email protected]> wrote: > On Mon, Jul 04, 2016 at 11:26:10AM +0100, Steven Kelso <[email protected]> > wrote: >> I've come across an issue when using the latest libev with gcc 5.3.0 >> under RedHat 6 and 7. It can be narrowed down to the following code: > > Hi! See "COMPILER WARNINGS" in the documentation. >
OK, I can see it now. I was reporting for a colleague was was running with full optimization for all of their code and re-reading the "Compiler Warnings" section I can see now why it's not a bug. I also agree with the 'uglifying' of code to make it compiler friendly for the same of readability is not the way to go as well. Thanks for your help. BTW, another way around the problem is to change our code being compiled to have the so that code can be compiled with -O3 and still work, in case anyone else finds it useful on the list: #pragma GCC diagnostic push #pragma GCC diagnostic ignored "-Wstrict-aliasing" #include <ev++.h> #pragma GCC diagnostic pop _______________________________________________ libev mailing list [email protected] http://lists.schmorp.de/mailman/listinfo/libev
