public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/102515] UBSAN misses signed division instrumentation Date: Tue, 28 Sep 2021 13:01:29 +0000 [thread overview] Message-ID: <bug-102515-4-t2IqDsb61y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102515-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102515 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- I see - I wonder whether we should do || sanitize_flags_p (SANITIZE_SI_OVERFLOW) for this specific case. For -ftrapv I also really was looking at instrumentation from the frontend rather than from pass_ubsan since that's quite late IMHO and so it doesn't help in removing hysterical avoidance of late "trap" introducing by the middle-end (though we do need to care anyway to not introduce undefined overflow). It also looks like handling ftrapv as Alias(fsanitize=...) doesn't work since we need to alias to two options. Meh ;) Maybe add fsanitize=trapv as a cover option for both. That said, I'm considering to pull the trigger on -ftrapv replacement by ubsan for GCC 12.
next prev parent reply other threads:[~2021-09-28 13:01 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-28 12:30 [Bug sanitizer/102515] New: " rguenth at gcc dot gnu.org 2021-09-28 12:48 ` [Bug sanitizer/102515] " jakub at gcc dot gnu.org 2021-09-28 13:01 ` rguenth at gcc dot gnu.org [this message] 2021-09-28 13:03 ` rguenth at gcc dot gnu.org 2021-10-01 10:00 ` rguenth at gcc dot gnu.org 2021-10-01 10:10 ` jakub at gcc dot gnu.org 2021-10-01 10:21 ` rguenth at gcc dot gnu.org 2021-10-01 10:21 ` rguenth at gcc dot gnu.org 2021-10-01 12:36 ` cvs-commit at gcc dot gnu.org 2021-10-04 16:04 ` rguenth at gcc dot gnu.org 2021-10-05 20:31 ` cvs-commit at gcc dot gnu.org 2022-05-10 8:21 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:22 ` cvs-commit 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-102515-4-t2IqDsb61y@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).