From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10305181623.AA25338@clio.rice.edu>
Subject: Re: GCC 3.3 & LIBC warning 1st pass
To: djgpp-workers AT delorie DOT com
Date: Sun, 18 May 2003 11:23:54 -0500 (CDT)
In-Reply-To: <002301c31cfb$6ebfabd0$0100a8c0@acp42g> from "Andrew Cottrell" at May 18, 2003 03:04:34 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> There are allot of the "dereferencing type-punned pointer will break
> strict-aliasing rules" issues with the LIBC source when built with GCC 3.3.

These come with -Wall ... is there some way we can turn off strict-aliasing?
I'd prefer to just remove that particular warning in the .opt file.  

Or set up some additional way to compile these modules with fewer 
checks?

> Info from the GCC 3.3. gcc.info file:-
> `-Wstrict-aliasing'
>      This option is only active when `-fstrict-aliasing' is active.  It
>      warns about code which might break the strict aliasing rules that
>      the compiler is using for optimization. The warning does not catch
>      all cases, but does attempt to catch the more common pitfalls. It
>      is included in `-Wall'.