https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111476
Sam James changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111476
--- Comment #7 from Sam James ---
I think slyfox's fix in 043a6fcbc27f8721301eb2f72a7839f54f393003 (PR111559)
sorted this, maybe?
I can't reproduce it anymore, anyway. Feel free to close as appropriate and
I'll reopen if it returns?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111476
Richard Biener changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #6 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111476
--- Comment #5 from Sam James ---
that commit looks to have just exposed it though as designed, the issue was
latent before I think
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111476
Sam James changed:
What|Removed |Added
Summary|[14 regression] ICE when|[14 regression] ICE when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111476
--- Comment #3 from Sam James ---
cvise just finished for me, `gcc -c util.i -O3`:
```
int ruby_strtod_c, ruby_strtod_nd;
double ruby_strtod_rv_0;
void ruby_strtod() {
int i, nz, z;
if (ruby_strtod_nd) {
nz = 0;
goto have_dig;
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111476
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111476
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
Target|
