> Bug #678122 [vim-gnome] vim-gnome: python bindings botched?

are there any compiler warnings with -O2? e.g. about strict aliasing violations?
If yes, please try building with -O2 -fno-strict-aliasing



--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4FE19578.4080900@debian.org">http://lists.debian.org/4FE19578.4080900@debian.org

On Wed, Jun 20, 2012 at 11:18:48AM +0200, Matthias Klose wrote:
> > Bug #678122 [vim-gnome] vim-gnome: python bindings botched?
>
> are there any compiler warnings with -O2? e.g. about strict aliasing violations?
> If yes, please try building with -O2 -fno-strict-aliasing

No compiler warnings and adding -fno-strict-aliasing doesn't help.

Cheers,
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan@debian.org>

On Wed, Jun 20, 2012 at 12:55:43PM +0200, Matthias Klose wrote:
> On 20.06.2012 12:29, James McCoy wrote:
> > On Wed, Jun 20, 2012 at 11:18:48AM +0200, Matthias Klose wrote:
> >>> Bug #678122 [vim-gnome] vim-gnome: python bindings botched?
> >>
> >> are there any compiler warnings with -O2? e.g. about strict aliasing violations?
> >> If yes, please try building with -O2 -fno-strict-aliasing
> >
> > No compiler warnings and adding -fno-strict-aliasing doesn't help.
>
> ok, now build everything with -O2, the one file with -O1,

Works.

> -O2 -fno-XXX,

Doesn't work.

> for every -f option which is enabled with -O2. I know, it's painful ...

I also tried "-O1 -fXXX" for all things listed under -O2 and that works.

Cheers,
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan@debian.org>