[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-08-05 Thread ktkachov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 ktkachov at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-24 Thread hubicka at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #13 from Jan Hubicka --- Author: hubicka Date: Thu Jul 24 13:50:31 2014 New Revision: 212991 URL: https://gcc.gnu.org/viewcvs?rev=212991&root=gcc&view=rev Log: PR lto/61802 * varasm.c (bss_initializer_p): Handle offlined ctor

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-24 Thread hubicka at ucw dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #12 from Jan Hubicka --- > > Yes, this fixes the failures on arm, will try aarch64 soon > > AArch64 seems to work fine too with this patch. Thanks! I will double check it and commit then. Honza

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-24 Thread ktkachov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #11 from ktkachov at gcc dot gnu.org --- (In reply to ktkachov from comment #10) > (In reply to Jan Hubicka from comment #9) > > Created attachment 33177 [details] > > Proposed patch > > > > I guess the problem is that error_mark_node

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-24 Thread ktkachov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #10 from ktkachov at gcc dot gnu.org --- (In reply to Jan Hubicka from comment #9) > Created attachment 33177 [details] > Proposed patch > > I guess the problem is that error_mark_node is special cased in varasm to > send symbols to B

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-23 Thread hubicka at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #9 from Jan Hubicka --- Created attachment 33177 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33177&action=edit Proposed patch I guess the problem is that error_mark_node is special cased in varasm to send symbols to BSS for

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-22 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #8 from Andrew Pinski --- (In reply to Jan Hubicka from comment #7) > Actually at the cauldron discussion I got an idea that it may be issue with > anchor generation > not bringing in all the constructors. Is the problem there that co

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-22 Thread hubicka at ucw dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #7 from Jan Hubicka --- Actually at the cauldron discussion I got an idea that it may be issue with anchor generation not bringing in all the constructors. Is the problem there that constructors of static vairables are empty in the fi

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-19 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #6 from Andrew Pinski --- This is definitely a section issue: .bss .align 3 .LANCHOR0 = . + 0 .type buf, %object .size buf, 10 buf: .hword 1 .hword 4 .hword 16 .h

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-18 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-15 Thread ktkachov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #4 from ktkachov at gcc dot gnu.org --- (In reply to Jan Hubicka from comment #3) > how those tests fail? They seem to hit abort (); signal 6 in the emulator

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-15 Thread hubicka at ucw dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #3 from Jan Hubicka --- how those tests fail?

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-15 Thread ktkachov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 ktkachov at gcc dot gnu.org changed: What|Removed |Added Target|aarch64-none-elf|aarch64-none-elf, arm* ---

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-15 Thread ktkachov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 --- Comment #1 from ktkachov at gcc dot gnu.org --- There's actually quite a lot of -flto failures (all of them?) besides the ones posted here all over the gcc testsuite

[Bug lto/61802] [4.10 Regression] AArch64 execute.exp failures with LTO after r212467

2014-07-15 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61802 Richard Biener changed: What|Removed |Added Keywords||lto, wrong-code Priority|P3