Re: [netlabs #726] -fno-strict-aliasing (fwd)

2002-06-23 Thread Nicholas Clark

On Sun, Jun 23, 2002 at 01:36:56AM -, Josh Wilmes wrote:
 # New Ticket Created by  Josh Wilmes 
 # Please include the string:  [netlabs #726]
 # in the subject line of all future correspondence about this issue. 
 # URL: http://bugs6.perl.org/rt2/Ticket/Display.html?id=726 
 
 
 
 --- Forwarded Message
 
 Date:Tue, 11 Jun 2002 15:21:06 +0100
 From:Nicholas Clark [EMAIL PROTECTED]

Well, that's one solution to Warnock's dilemma :-)

No, in the intervening time I've not found an answer to my original questions.
Sorry. :-(

Nicholas Clark
-- 
Even better than the real thing:http://nms-cgi.sourceforge.net/



[netlabs #726] -fno-strict-aliasing (fwd)

2002-06-22 Thread via RT

# New Ticket Created by  Josh Wilmes 
# Please include the string:  [netlabs #726]
# in the subject line of all future correspondence about this issue. 
# URL: http://bugs6.perl.org/rt2/Ticket/Display.html?id=726 



--- Forwarded Message

Date:Tue, 11 Jun 2002 15:21:06 +0100
From:Nicholas Clark [EMAIL PROTECTED]
To:  [EMAIL PROTECTED]
Subject: -fno-strict-aliasing

Configure.pl is pulling perl5's C compiler flags in without question.
perl5 is defining -fno-strict-aliasing on gcc.

1: As parrot is trying to be as clean as possible in its source, and
   rules about aliasing (and what a compiler may assume) is part of ANSI
   C, why do we need this flag?
2: Is it possible to get gcc (or any other compiler) to issue warnings where
   it detects that strict aliasing would (or might) change the program
   result?

Nicholas Clark

--- End of Forwarded Message