This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: No warning of violating strict aliasing rule and produce wrong code

From: Andrew Haley <aph at redhat dot com>
To: Bingfeng Mei <bmei at broadcom dot com>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 30 Jun 2008 14:00:18 +0100
Subject: Re: No warning of violating strict aliasing rule and produce wrong code
References: <2E073B3ABB3F664DBA1D1C4D5FB47EF40E60F5D3@NT-IRVA-0752.brcm.ad.broadcom.com> <4868D557.70205@redhat.com> <2E073B3ABB3F664DBA1D1C4D5FB47EF40E60F5D9@NT-IRVA-0752.brcm.ad.broadcom.com>

Bingfeng Mei wrote:
> Sorry, I made a mistake. My local copy of mainline version (still 4.3.0
> 20080213) doesn't gave warning. I just updated my mainline GCC and it
> does give warning now. 

I think that you'll find the release 4.3 version does too.

While we try to ensure that gcc warns whenever it can about incorrect pointer
conversions, we certainly don't do so in all cases, and the general case is,
I suspect, incomputable.

Andrew.

References:
- No warning of violating strict aliasing rule and produce wrong code
  - From: Bingfeng Mei
- Re: No warning of violating strict aliasing rule and produce wrong code
  - From: Andrew Haley
- RE: No warning of violating strict aliasing rule and produce wrong code
  - From: Bingfeng Mei

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]