public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/44786] -fcatch-undefined-behavior: Turn on runtime code generation to check for undefined behavior Date: Sun, 08 Apr 2012 14:06:00 -0000 [thread overview] Message-ID: <bug-44786-4-cyoakFRDXZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44786-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44786 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-04-08 14:06:31 UTC --- Indeed. I think it's meant to be useful for catching some of the problems that valgrind identifies, and valgrind has even more performance overhead. That said, although I haven't used it heavily clang's -fcatch-undefined-behavior has never caught any problems for me. YMMV.
next prev parent reply other threads:[~2012-04-08 14:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44786-4@http.gcc.gnu.org/bugzilla/> 2012-04-08 12:11 ` vanyacpp at gmail dot com 2012-04-08 14:06 ` redi at gcc dot gnu.org [this message] 2012-04-08 18:58 ` [Bug middle-end/44786] " pinskia at gcc dot gnu.org 2012-11-08 12:53 ` markus at trippelsdorf dot de 2012-11-08 13:22 ` [Bug middle-end/44786] -fsanitize=undefined: " manu at gcc dot gnu.org 2014-04-25 8:20 ` vincent-gcc at vinc17 dot net 2014-04-25 8:28 ` mpolacek at gcc dot gnu.org 2014-08-21 6:55 ` mpolacek at gcc dot gnu.org 2010-07-02 16:47 [Bug c++/44786] New: -fcatch-undefined-behavior: " manu at gcc dot gnu dot org 2010-07-05 1:22 ` [Bug c++/44786] " pinskia at gcc dot gnu dot org 2010-07-23 20:41 ` joseph at codesourcery dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-44786-4-cyoakFRDXZ@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).