[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Change by Irit Katriel : -- resolution: -> fixed stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bug

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Irit Katriel added the comment: I think this was resolved by issue9189. -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___ ___

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Mark Lawrence added the comment: Is this still relevant as GCC 4.9.0 was released on April 22, 2014? -- nosy: +BreamoreBoy ___ Python tracker ___ _

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Marc-Andre Lemburg added the comment: Matthias Klose wrote: > > Matthias Klose added the comment: > > my understanding is that the builder is allowed to overwrite OPT, but not > BASECFLAGS. The builder should actually be allowed to override the complete CFLAGS and LDFLAGS settings, but for

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Matthias Klose added the comment: my understanding is that the builder is allowed to overwrite OPT, but not BASE_CFLAGS. -- ___ Python tracker ___ __

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Marc-Andre Lemburg added the comment: Matthias Klose wrote: > > Matthias Klose added the comment: > >> It's probably better to just pass OPT to the linker instead. > > not enough, because -fno-strict-aliasing might be passed in BASE_CFLAGS. Shouldn't -fno-strict-aliasing be added to OPT ins

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Roumen Petrov added the comment: LDSHARED not always is compiler and I'm not sure that linkers always accept compiler flags . After fix of issue xxx about CFLAGS and issues a, b, c, for LDFLAGS now all is passed to python build system and users could set argument to both variables : CFLAGS an

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Matthias Klose added the comment: > It's probably better to just pass OPT to the linker instead. not enough, because -fno-strict-aliasing might be passed in BASE_CFLAGS. -- ___ Python tracker _

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

Marc-Andre Lemburg added the comment: Matthias Klose wrote: > > New submission from Matthias Klose : > > Building with -flto (GCC 4.5.0) requires passing the very same optimization > flags to the linker (lto1) as well. The attached patch just does this. > Tested on Linux only, I don't know

[issue8535] passing optimization flags to the linker required for builds with gcc -flto

New submission from Matthias Klose : Building with -flto (GCC 4.5.0) requires passing the very same optimization flags to the linker (lto1) as well. The attached patch just does this. Tested on Linux only, I don't know what will/could break on on other systems/compilers. Tested with a static