cast question, again

Alejandro Mery amery at
Mon Sep 29 10:51:33 CEST 2008

On Mon, Sep 29, 2008 at 3:58 AM, Marc Lehmann <schmorp at> wrote:
> On Mon, Sep 29, 2008 at 02:00:20AM +0200, Alejandro Mery <amery at> wrote:
>> I'm using -fno-strict-aliasing now to make gcc behave as a C compiler :)
> gcc tries to behave like a c compiler with or without that switch, that
> switch will not make any difference here.
> What you meant is that you made gcc accept your _buggy_, non-C code as if
> it were valid C, and try it's best to not misoptimise it, despite it having
> severe bugs.
> I know it's easy to deceive oneself, but the fact remains that your code is
> now buggy, thanks to the policy you are trying to follow.

may I ask who's the buggy-code-maker from "-Os -fno-strict-aliasing
-Werror -Wall  -W" exactly?

what do you suggest to add or remove to make gcc not produce "buggy" code?

More information about the libev mailing list