This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: type based aliasing again
- To: mark at codesourcery dot com
- Subject: Re: type based aliasing again
- From: jlarmour at cygnus dot co dot uk (Jonathan Larmour)
- Date: Sun, 12 Sep 1999 17:44:25 +0100
- Cc: rms at gnu dot org, jbuck at synopsys dot com, gcc at gcc dot gnu dot org
- Newsgroups: cygnus.egcs
- Organization: Cygnus Solutions Ltd, UK
- References: <199909100708.AAA00030@atrus.synopsys.com><199909110724.DAA03071@psilocin.gnu.org>
In article <19990911152505P.mitchell@codesourcery.com> you write:
>
>Someone (not RMS, but I have lost track of who, originally) wrote:
>
> In the end, if your argument is carried too far, the
> only solution would be to make -fno-strict-alias the
> default.
>
>I think that making -fno-strict-aliasing the default is sensible
>proposal, and worth debating.
Also remember that -fno-strict-aliasing may not be enough to make user
code that breaks the alias rules work. As I said elsewhere, I believe
the instruction scheduler makes assumptions about aliasing of scalars
and structs.
For that reason, I think the warning may be a better way to go because
it may be able to catch these cases as well.
Jifl
--
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK. Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
my brains kept falling out." || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/ These opinions are all my own fault