https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58489
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2015-01-23 CC| |ramana at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #3 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> --- (In reply to Timo Teräs from comment #2) > I got this fixed. It seems genautomata does not work properly if it is built > with -fPIC. Since PIE/PIC get added automatically in alpine toolchain it > caused this. > > For now I'm adding explicitly -fno-PIC to genautomata compilation. However, > it would be better if genautomata could be fixed to: > - abort compilation if genautomata failed to do it's job properly > - fix genautomata to work even if compiled with -fPIC Interesting observation and interesting that the "broken automaton" managed to build the whole of gcc and the run time support libraries in gcc and presumably glibc. If it was genautomata that doesn't work properly when built with PIC can you reduce the failure point in genautomata. Without more details or better input testcases it's very hard to reduce this in any other way or form especially as I cannot reproduce the issue with a new top of tree 4.8 toolchain.