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]

Re: aliasing warnings [patch]

To: oliva AT lsd.ic.unicamp.br
Subject: Re: aliasing warnings [patch]
From: craig AT jcb-sc dot com
Date: 16 Sep 1999 18:40:12 -0000
cc: mark AT codesourcery dot com, zack AT bitmover dot com, egcs AT egcs.cygnus dot com, egcs-patches AT egcs.cygnus dot com
cc: craig AT jcb-sc dot com
References: <199909161637.JAA15001@zack.bitmover.com> <19990916101540T.mitchell@codesourcery.com> <orvh9ayd92.fsf@cupuacu.lsd.ic.unicamp.br>

>> I don't think this warning should be on by default
>
>-Wall, maybe?  Or maybe we should really enable it by default, so that
>people will be warned about the problem sooner rather than too late.
>We could always provide an option to disable it.

Given all the heat over the issue, especially involving claims about
"canned" free software using GCC to build from source, it seems like
a substantial portion of the target audience for these warnings would
be completely missed *unless* we enabled this option by default,
and shipped this as GCC 2.95.2.

Of course, we have to make sure the warnings are appropriately
generated or not per language, etc., the usual cleaning-up.

        tq vm, (burley)

References:
- aliasing warnings [patch]
  - From: Zack Weinberg
- Re: aliasing warnings [patch]
  - From: Mark Mitchell
- Re: aliasing warnings [patch]
  - From: Alexandre Oliva

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