[Bug c++/53294] Optimize out some exception code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53294 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE See Also||https://gcc.gnu.org/bugzill ||a/show_bug.cgi?id=38658 Status|NEW |RESOLVED --- Comment #5 from Andrew Pinski --- Dup of bug 38658. *** This bug has been marked as a duplicate of bug 38658 ***
[Bug c++/53294] Optimize out some exception code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53294 Martin Sebor changed: What|Removed |Added CC||federico.kircheis at gmail dot com --- Comment #4 from Martin Sebor --- *** Bug 90029 has been marked as a duplicate of this bug. ***
[Bug c++/53294] Optimize out some exception code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53294 --- Comment #3 from Antony Polukhin --- Any progress?
[Bug c++/53294] Optimize out some exception code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53294 --- Comment #2 from Antony Polukhin --- *** Bug 82504 has been marked as a duplicate of this bug. ***
[Bug c++/53294] Optimize out some exception code
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53294 Richard Guenther changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed||2012-05-09 Ever Confirmed|0 |1 --- Comment #1 from Richard Guenther 2012-05-09 13:55:37 UTC --- Certainly interesting. We lower things too early into __cxa calls though (I think) to make this work easily. Consider cases like struct X { int i; }; int foo (void) { try { X x; x.i = 5; throw x; } catch (X& x) { return x.i; } catch (...) { return 0; } }