public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/44786] New: -fcatch-undefined-behavior: Turn on runtime code generation to check for undefined behavior Date: Fri, 02 Jul 2010 16:47:00 -0000 [thread overview] Message-ID: <bug-44786-13511@http.gcc.gnu.org/bugzilla/> (raw) Clang provides a number of ways to control code generation. The options are listed below. -fcatch-undefined-behavior: Turn on runtime code generation to check for undefined behavior. This option, which defaults to off, controls whether or not Clang adds runtime checks for undefined runtime behavior. If the check fails, __builtin_trap() is used to indicate failure. The checks are: # Subscripting where the static type of one operand is variable which is decayed from an array type and the other operand is greater than the size of the array or less than zero. # Shift operators where the amount shifted is greater or equal to the promoted bit-width of the left-hand-side or less than zero. # If control flow reaches __builtin_unreachable. -- Summary: -fcatch-undefined-behavior: Turn on runtime code generation to check for undefined behavior Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: manu at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44786
next reply other threads:[~2010-07-02 16:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-02 16:47 manu at gcc dot gnu dot org [this message] 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-13511@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).