[Bug c++/89561] feature request: undefined behaviour compile-time configuration

2019-03-04 Thread bugsthecode at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89561 --- Comment #8 from bugsthecode at mail dot ru --- (In reply to Martin Sebor from comment #7) > It's not possible to detect all instances of undefined behavior and emit > some "reasonable" or "safe" code (whatever that might mean in each > instanc

[Bug c++/89561] feature request: undefined behaviour compile-time configuration

2019-03-04 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89561 --- Comment #7 from Martin Sebor --- It's not possible to detect all instances of undefined behavior and emit some "reasonable" or "safe" code (whatever that might mean in each instance), certainly not without compromising efficiency. Timing a p

[Bug c++/89561] feature request: undefined behaviour compile-time configuration

2019-03-04 Thread bugsthecode at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89561 bugsthecode at mail dot ru changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|

[Bug c++/89561] feature request: undefined behaviour compile-time configuration

2019-03-04 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89561 Richard Biener changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/89561] feature request: undefined behaviour compile-time configuration

2019-03-02 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89561 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment

[Bug c++/89561] feature request: undefined behaviour compile-time configuration

2019-03-02 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89561 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|