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:22:21 +0300 From: Eli Zaretskii Subject: Re: Some patches to DJGPP v2.04 (GCC-4.4.1 related) In-reply-to: <647fe9b10908010310of9d1a72k46c228264ead30de@mail.gmail.com> X-012-Sender: halo1 AT inter DOT net DOT il To: djgpp-workers AT delorie DOT com Message-id: <83hbwrq1eq.fsf@gnu.org> References: <4A73E13E DOT 3050700 AT iki DOT fi> <647fe9b10908010147j1cc16f97o7dc9ff609387cc3 AT mail DOT gmail DOT com> <83k51nq2cd DOT fsf AT gnu DOT org> <647fe9b10908010310of9d1a72k46c228264ead30de 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 13:10:13 +0300 > From: Ozkan Sezer > > Miscommunication, I think: What I suggest is that one > shouldn't rely plainly on -Wall to see strict aliasing > warnings, but also use -Wstrict-aliasing=2 to see if > there are more. If you miss those warnings, you _may_ > (or may not) end up having bad binaries. Besides, > in some cases, even -Wstrict-aliasing=2 doesn't > report the aliasing violations and gcc can silently > generate bad code. I hope this was clear enough. Yes, this is clear. Thanks, and sorry for my misunderstanding.