https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82952
Marek Polacek changed:
What|Removed |Added
CC||sshannin at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82952
Jakub Jelinek changed:
What|Removed |Added
CC||joerg.rich...@pdv-fs.de
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82952
Volker Reichelt changed:
What|Removed |Added
CC||reichelt at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82952
--- Comment #5 from Richard Biener ---
(In reply to Jakub Jelinek from comment #4)
> Yeah, indeed. I'd say in this case the biggest problem is probably repeated
> traversal of SAVE_EXPRs in inchash::add_expr (which BTW doesn't seem to be
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82952
Jakub Jelinek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82952
Richard Biener changed:
What|Removed |Added
Keywords||compile-time-hog
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82952
Ahmad Fatoum changed:
What|Removed |Added
Target||x86_64-pc-linux-gnu
Host|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82952
--- Comment #1 from Ahmad Fatoum ---
Created attachment 42587
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42587=edit
File that hangs g++
I didn't manage to reduce it by much, because of the halting problem. At least
it reliably shows
