[Bug c/109426] Gcc runs into Infinite loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109426 --- Comment #6 from Jonathan Wakely --- It's a pattern with this person: https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&cf_known_to_fail_type=allwords&cf_known_to_work_type=allwords&email1=zhonghao%40pku.org.cn&emailreporter1=1&emailtype1=substring&list_id=377697&product=gcc&query_format=advanced&resolution=INVALID See PR 86306 for discussion and their justification for these low quality reports. I think they're genuinely trying to be helpful, just not succeeding.
[Bug c/109426] Gcc runs into Infinite loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109426 --- Comment #5 from Xi Ruoyao --- (In reply to Jonathan Wakely from comment #4) > N.B. this code is just copied from PR 54402. It might have been helpful to > say where you found the code. > > zhonghao, it's really not helpful to just copy&paste code that you don't > understand into bug reports with stupid, incorrect claims like "while > expanding templates". Maybe you're trying to be helpful, but you're just > wasting our time. I'm wondering if this is an attempt for some kind of "academic research" here like the notorious UMN incident in LKML.
[Bug c/109426] Gcc runs into Infinite loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109426 --- Comment #4 from Jonathan Wakely --- N.B. this code is just copied from PR 54402. It might have been helpful to say where you found the code. zhonghao, it's really not helpful to just copy&paste code that you don't understand into bug reports with stupid, incorrect claims like "while expanding templates". Maybe you're trying to be helpful, but you're just wasting our time.
[Bug c/109426] Gcc runs into Infinite loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109426 Xi Ruoyao changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||xry111 at gcc dot gnu.org Resolution|--- |INVALID --- Comment #3 from Xi Ruoyao --- (In reply to Andrew Pinski from comment #2) > There is no infinite loop and the code finally completes. > > You are causing an warnings of over 2x warning messages with the macros. > This will be slow. Looks like it's slow not only because of the warnings. The preprocessed code is 1.6M and it's slow even with -w (62.76s with 12.2.0). > > I don't run into an infinite loop at all on the trunk. Anyway this is INVALID. You cannot assume any compiler able to compile such a compiler bomb efficiently.
[Bug c/109426] Gcc runs into Infinite loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109426 Andrew Pinski changed: What|Removed |Added Component|c++ |c --- Comment #2 from Andrew Pinski --- There is no infinite loop and the code finally completes. You are causing an warnings of over 2x warning messages with the macros. This will be slow. I don't run into an infinite loop at all on the trunk.
[Bug c++/109426] Gcc runs into Infinite loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109426 Andrew Pinski changed: What|Removed |Added Summary|Gcc runs into Infinite |Gcc runs into Infinite loop |loop, when resolving| |templates | --- Comment #1 from Andrew Pinski --- The code example you provided does not have any templates ...
