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: strict aliasing question

From: Mike Stump <mrs at apple dot com>
To: Howard Chu <hyc at highlandsun dot com>
Cc: Richard Guenther <richard dot guenther at gmail dot com>, gcc at gcc dot gnu dot org
Date: Fri, 10 Nov 2006 13:52:15 -0800
Subject: Re: strict aliasing question
References: <45545354.2000706@highlandsun.com> <84fc9c000611100244t10761e03nf8cdbf1d67b2637c@mail.gmail.com> <4554BB76.2080801@highlandsun.com>

On Nov 10, 2006, at 9:48 AM, Howard Chu wrote:

Richard Guenther wrote:
If you compile with -O3 -combine *.c -o alias it will break.

Thanks for pointing that out. But that's not a realistic danger for the actual application. The accessor function is always going to be in a library compiled at a separate time. The call will always be from a program built at a separate time, so -combine isn't a factor.

We are building a compiler to outsmart you. We presently working on technology (google ("LTO")) to break your code. :-) Don't cry when we turn it on by default and it does. I'd recommend understanding the rules and following them.

Follow-Ups:
- Re: strict aliasing question
  - From: Howard Chu
- Re: strict aliasing question
  - From: Howard Chu

References:
- strict aliasing question
  - From: Howard Chu
- Re: strict aliasing question
  - From: Richard Guenther
- Re: strict aliasing question
  - From: Howard Chu

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