public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "i at maskray dot me" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109489] New: [ubsan] Support -fsanitize-trap= Date: Wed, 12 Apr 2023 18:07:55 +0000 [thread overview] Message-ID: <bug-109489-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109489 Bug ID: 109489 Summary: [ubsan] Support -fsanitize-trap= Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: i at maskray dot me Target Milestone: --- Clang has supported -fsanitize-trap=undefined and many fine-grained options[1] e.g. -fsanitize-trap=alignment since 2015. -fsanitize-undefined-trap-on-error is a deprecated alias for -fsanitize-trap=undefined in Clang. -fsanitize-trap= provides fine-grained control over putting specific checks into the trap mode, and it provides a unified interface with -fsanitize= and -fsanitize-recover=. As an example, -fsanitize=undefined in the normal mode may increase the binary size a lot. The user may put some checks into the trap mode while keeping the rest in the normal mode (-fsanitize-trap=alignment,null) to make the binary smaller. [1]: https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html
next reply other threads:[~2023-04-12 18:07 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-12 18:07 i at maskray dot me [this message] 2023-04-12 18:09 ` [Bug sanitizer/109489] " pinskia at gcc dot gnu.org 2023-04-17 4:22 ` i at maskray dot me 2023-04-17 4:59 ` pinskia at gcc dot gnu.org
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-109489-4@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).