linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-ppc@lauterbach.com>
To: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
Cc: Andreas Schwab <schwab@suse.de>, linuxppc-dev@lists.linuxppc.org
Subject: Re: asm inline
Date: Mon, 02 Dec 2002 16:35:05 +0100	[thread overview]
Message-ID: <5.2.0.9.2.20021202162114.01d3dad0@mail.lauterbach.com> (raw)
In-Reply-To: <200212021011.55105.kevin.hendricks@sympatico.ca>


At 16:11 02.12.2002, Kevin B. Hendricks wrote:

>Hi,
>
>Here is what Sun's Hamburg developers wrote in reply...
>
> > Hi Kevin,
> >
> > -fstrict-aliasing is in -O2 optimization since gcc-3.0.x. And no, our
> > code is not strict alias safe. You'll get some problems, I know of at
> > least one place in sc. I bet there are more.
> >
> > I recommend to use -O2 -fno-strict-aliasing. This is what Hamburg
> > release engineering currently uses.
> >
> > If someone is able to identify all strict alias violating places I would
> > be more than happy to propose that we change these (or add the
> > -fno-strict-alias to just these files).
> >
> > Heiner
>
>So it looks like Solaris and Win must not detect these issues already.
>So a backport of the gcc 3.3 warning flag would certainly be a big help to
>the OOo project as well.

I see, but I think there is no chance that this is backported to an
official 3.2 release. Also 3.3 is only a few month away, so it makes no
real sense.

Franz.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-12-02 15:35 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
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 [this message]
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=5.2.0.9.2.20021202162114.01d3dad0@mail.lauterbach.com \
    --to=franz.sirl-ppc@lauterbach.com \
    --cc=kevin.hendricks@sympatico.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schwab@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).