[Bug target/95381] [11 Regression]: Build fails with --disable-bootstrap on m68k with ICE: in operator[], at vec.h:867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381 Richard Biener changed: What|Removed |Added Known to work||12.0 Resolution|--- |FIXED Known to fail||11.5.0 Target Milestone|11.5|12.0 Status|NEW |RESOLVED --- Comment #23 from Richard Biener --- Fixed in GCC 12 it seems.
[Bug target/95381] [11 Regression]: Build fails with --disable-bootstrap on m68k with ICE: in operator[], at vec.h:867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381 Jakub Jelinek changed: What|Removed |Added Target Milestone|11.4|11.5 --- Comment #22 from Jakub Jelinek --- GCC 11.4 is being released, retargeting bugs to GCC 11.5.
[Bug target/95381] [11 Regression]: Build fails with --disable-bootstrap on m68k with ICE: in operator[], at vec.h:867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381 Eric Gallager changed: What|Removed |Added Summary|[11/12/13 Regression]: |[11 Regression]: Build |Build fails with|fails with |--disable-bootstrap on m68k |--disable-bootstrap on m68k |with ICE: in operator[], at |with ICE: in operator[], at |vec.h:867 |vec.h:867 CC||egallager at gcc dot gnu.org Keywords||build --- Comment #21 from Eric Gallager --- (In reply to John Paul Adrian Glaubitz from comment #20) > JIT definitely works with 12 on m68k again - and probably 13. So, the title > is misleading. ok, retitled
[Bug target/95381] [11 Regression]: Build fails with --disable-bootstrap on m68k with ICE: in operator[], at vec.h:867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381 Richard Biener changed: What|Removed |Added Priority|P3 |P4
[Bug target/95381] [11 Regression]: Build fails with --disable-bootstrap on m68k with ICE: in operator[], at vec.h:867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381 Jeffrey A. Law changed: What|Removed |Added Status|WAITING |NEW --- Comment #16 from Jeffrey A. Law --- I've been able to reproduce this. It's either the enabling jit or host shared libraries (which is required to enable jit). It's faulting in the escaped string tests which makes sense given John's bisection info. I'm debugging in the background as this isn't anywhere near the top of my todo list.
