[Bug target/98210] [11 Regression] SHF_GNU_RETAIN breaks gold linker generated binaries

2021-02-19 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98210 Jozef Lawrynowicz changed: What|Removed |Added Resolution|--- |WONTFIX Status|REOPENED

[Bug target/98210] [11 Regression] SHF_GNU_RETAIN breaks gold linker generated binaries

2021-02-19 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98210 --- Comment #9 from Jozef Lawrynowicz --- I believe this PR only relates to the fact that GCC support for SHF_GNU_RETAIN was available before GOLD supported that section flag. My proposed patch was to turn off GCC support for SHF_GNU_RETAIN if a

[Bug target/98210] [11 Regression] SHF_GNU_RETAIN breaks gold linker generated binaries

2020-12-16 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98210 --- Comment #6 from Jozef Lawrynowicz --- I've posted a patch where the HAVE_GAS_SHF_GNU_RETAIN configure test has been extended to check for SHF_GNU_RETAIN gold support: https://gcc.gnu.org/pipermail/gcc-patches/2020-December/562100.html

[Bug target/98210] [11 Regression] SHF_GNU_RETAIN breaks gold linker generated binaries

2020-12-15 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98210 --- Comment #4 from Jozef Lawrynowicz --- Since gold is not built by default, should we just disable SHF_GNU_RETAIN support if gold has been built at all, for Binutils versions without the gold patch. There's 2 weeks between the GCC "used" imply

[Bug target/98121] [11 Regression] __attribute__ ((used)) should not imply SHF_RETAIN_SECTION

2020-12-04 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98121 Jozef Lawrynowicz changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW

[Bug target/98146] New: [11 Regression] section type conflict when "used" attribute is applied to decl with specific section

2020-12-04 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98146 Bug ID: 98146 Summary: [11 Regression] section type conflict when "used" attribute is applied to decl with specific section Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug other/98121] __attribute__ ((used)) should not imply SHF_RETAIN_SECTION

2020-12-03 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98121 --- Comment #8 from Jozef Lawrynowicz --- (In reply to Jozef Lawrynowicz from comment #7) > (In reply to Florian Weimer from comment #6) > > (In reply to Jozef Lawrynowicz from comment #4) > > > GAS merges the "R" flag state in .section declarati

[Bug other/98121] __attribute__ ((used)) should not imply SHF_RETAIN_SECTION

2020-12-03 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98121 --- Comment #7 from Jozef Lawrynowicz --- (In reply to Florian Weimer from comment #6) > (In reply to Jozef Lawrynowicz from comment #4) > > GAS merges the "R" flag state in .section declarations, silently, and with > > logical OR, and GCC should

[Bug other/98121] __attribute__ ((used)) should not imply SHF_RETAIN_SECTION

2020-12-03 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98121 --- Comment #4 from Jozef Lawrynowicz --- (In reply to H.J. Lu from comment #2) > The issue here is that what should happen when definitions marked with used > attribute and unmarked definitions are put in the same section. It has > nothing > to

[Bug target/98121] __attribute__ ((used)) should not imply SHF_RETAIN_SECTION

2020-12-03 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98121 jozefl at gcc dot gnu.org changed: What|Removed |Added CC||jozefl at gcc dot gnu.org ---

[Bug libstdc++/97798] FTB msp430-elf error: the value of '__gnu_cxx::__numeric_traits_integer<__int20>::__max' is not usable in a constant expression

2020-11-13 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97798 --- Comment #23 from jozefl at gcc dot gnu.org --- (In reply to Jonathan Wakely from comment #22) > I tested the patches on x86_64-linux and confirmed that the branches can > bootstrap msp430-elf, so I went ahead and pushed them. > > If you're no

[Bug libstdc++/97798] FTB msp430-elf error: the value of '__gnu_cxx::__numeric_traits_integer<__int20>::__max' is not usable in a constant expression

2020-11-13 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97798 --- Comment #19 from jozefl at gcc dot gnu.org --- (In reply to Jonathan Wakely from comment #18) > The patch will apply cleanly to gcc-10 but not gcc-9. Let me know if you > want me to prepare a patch for the gcc-9 branch. If it's not too much w

[Bug libstdc++/97798] FTB msp430-elf error: the value of '__gnu_cxx::__numeric_traits_integer<__int20>::__max' is not usable in a constant expression

2020-11-12 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97798 --- Comment #16 from jozefl at gcc dot gnu.org --- (In reply to Jonathan Wakely from comment #15) > Hmm, I get the same error for a out-of-tree binutils built from today's git > sources: > > GNU assembler (GNU Binutils) 2.35.50.20201112 > Copyrig

[Bug libstdc++/97798] FTB msp430-elf error: the value of '__gnu_cxx::__numeric_traits_integer<__int20>::__max' is not usable in a constant expression

2020-11-12 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97798 --- Comment #14 from jozefl at gcc dot gnu.org --- (In reply to Jonathan Wakely from comment #13) > I tried a bootstrap of gcc-10 and I get this error during libgcc/configure > > conftest.s: Assembler messages: > conftest.s:168: Error: unknown ps

[Bug libstdc++/97798] FTB msp430-elf error: the value of '__gnu_cxx::__numeric_traits_integer<__int20>::__max' is not usable in a constant expression

2020-11-12 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97798 --- Comment #12 from jozefl at gcc dot gnu.org --- Thanks! I've set off a full msp430-elf build and regtest. I'll look at backporting it to GCC8/9/10 branches after testing.

[Bug libstdc++/97798] FTB msp430-elf error: the value of '__gnu_cxx::__numeric_traits_integer<__int20>::__max' is not usable in a constant expression

2020-11-12 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97798 --- Comment #9 from jozefl at gcc dot gnu.org --- (In reply to Jonathan Wakely from comment #8) > My attempt to build msp430 fails with: > > In file included from > /home/jwakely/gcc/msp430-elf/msp430-elf/include/stdint.h:13, > f

[Bug c++/97798] FTB msp430-elf error: the value of '__gnu_cxx::__numeric_traits_integer<__int20>::__max' is not usable in a constant expression

2020-11-11 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97798 --- Comment #2 from jozefl at gcc dot gnu.org --- Created attachment 49547 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49547&action=edit tester.ii (In reply to Marek Polacek from comment #1) > Would it be possible to provide a preprocess

[Bug c++/97798] New: FTB msp430-elf error: the value of '__gnu_cxx::__numeric_traits_integer<__int20>::__max' is not usable in a constant expression

2020-11-11 Thread jozefl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97798 Bug ID: 97798 Summary: FTB msp430-elf error: the value of '__gnu_cxx::__numeric_traits_integer<__int20>::__max' is not usable in a constant expression Product: gcc