From: Andreas Schwab <schwab@suse.de>
To: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: asm inline
Date: Mon, 02 Dec 2002 15:29:47 +0100 [thread overview]
Message-ID: <jeisycebok.fsf@sykes.suse.de> (raw)
In-Reply-To: <200212020914.21465.kevin.hendricks@sympatico.ca> ("Kevin B. Hendricks"'s message of "Mon, 2 Dec 2002 09:14:21 -0500")
"Kevin B. Hendricks" <kevin.hendricks@sympatico.ca> writes:
|> Hi,
|>
|> I thought strict-aliasing was only turned on at -O3?
|> It was that way in the past. Did this change for gcc-3.2.X?
Yes, strict aliasing is now the default.
|> There seems to be an enormous amount of code that is not strict-aliasing
|> safe (in the JDK, in OpenOffice.org, etc).
Well, they have always walked on thin ice...
|> Is there any warning flag that can be enabled to help find these cases (the
|> OOo source base is simply huge)?
gcc 3.3 implements such a warning, but it may give many false positives.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-02 14:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 16:08 asm inline Samuel Rydh
2002-11-29 16:21 ` Gabriel Paubert
2002-11-29 17:49 ` Samuel Rydh
2002-12-02 11:17 ` Franz Sirl
2002-12-02 13:11 ` Samuel Rydh
2002-12-02 13:35 ` Andreas Schwab
2002-12-02 14:14 ` Kevin B. Hendricks
2002-12-02 14:29 ` Andreas Schwab [this message]
2002-12-02 14:37 ` Kevin B. Hendricks
2002-12-02 14:51 ` Franz Sirl
2002-12-02 15:08 ` Kevin B. Hendricks
2002-12-02 15:11 ` Kevin B. Hendricks
2002-12-02 15:35 ` Franz Sirl
2002-12-02 15:45 ` Kevin B. Hendricks
2002-12-02 15:12 ` Franz Sirl
2002-12-02 17:00 ` Samuel Rydh
2002-12-02 17:53 ` Gabriel Paubert
2002-12-02 19:17 ` Samuel Rydh
2002-11-29 16:30 ` Benjamin Herrenschmidt
2002-12-02 14:29 ` Gabriel Paubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jeisycebok.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=kevin.hendricks@sympatico.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.