[Bug middle-end/114391] catch() and immediate throw; could be optimized to noop

2024-03-19 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114391 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement CC|

[Bug middle-end/114391] catch() and immediate throw; could be optimized to noop

2024-03-19 Thread antoshkka at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114391 --- Comment #2 from Antony Polukhin --- > Is there something to optimize when foo() cannot be tail-called? Yes. Just `catch (...) { throw; }`, no more restrictions. I do not even think, that it should be the outer most EH region: void foo();

[Bug middle-end/114391] catch() and immediate throw; could be optimized to noop

2024-03-19 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114391 Richard Biener changed: What|Removed |Added Last reconfirmed||2024-03-19 Status|UNCONFIR