X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient: djgpp-workers AT delorie DOT com
Date: Sat, 01 Aug 2009 13:02:10 +0300
From: Eli Zaretskii <eliz AT gnu DOT org>
Subject: Re: Some patches to DJGPP v2.04 (GCC-4.4.1 related)
In-reply-to: <647fe9b10908010147j1cc16f97o7dc9ff609387cc3@mail.gmail.com>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-id: <83k51nq2cd.fsf@gnu.org>
References: <4A73E13E DOT 3050700 AT iki DOT fi> <647fe9b10908010147j1cc16f97o7dc9ff609387cc3 AT mail DOT gmail DOT com>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Date: Sat, 1 Aug 2009 11:47:59 +0300
> From: Ozkan Sezer <sezeroz AT gmail DOT com>
> 
> Although you may want to build using
> -Wstrict-aliasing=2 before finishing your work, because gcc
> seems to hide some of the warnings _and_ may generate
> bad code, and in some worse cases may not warn even
> with that warning flag and still generate bad code which
> happened to me once (that was with gcc-4.5, though..)

Details, please: how can a warning option cause bad code generation?