asm inline

Kevin B. Hendricks kevin.hendricks at
Tue Dec 3 02:11:55 EST 2002


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.



On December 2, 2002 09:51, Franz Sirl wrote:
> At 15:37 02.12.2002, Kevin B. Hendricks wrote:
> >Hi,
> >
> > > |> 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.
> >
> >Any chance we can get this flag backported so that it appears in gcc
> > 3.2.2?
> >
> >False positives are a whole lot better than code that quietly does the
> > an unexpected thing.
> Well, are you sure OO is really affected? strict-aliasing is the default
> since gcc-2.96 which means that everything since redhat-7.0 would be
> affected on x86 for example. Also GCC has been very late to make this
> the default at all, I think that Sun and MS compilers do this for years
> already. I would be very surprised if a multiplatform project like OO
> still contained reasonable amounts of aliasing-unsafe code.
> Franz.

** Sent via the linuxppc-dev mail list. See

More information about the Linuxppc-dev mailing list