public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Wed, 11 May 2022 06:22:38 +0000 [thread overview]
Message-ID: <bug-102515-4-hKdUoxHr3K@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 #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:f806bea0a6c1c5b7d517c7aee053c21b4d2155c6
commit r9-10103-gf806bea0a6c1c5b7d517c7aee053c21b4d2155c6
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Oct 1 14:27:32 2021 +0200
ubsan: Use -fno{,-}sanitize=float-divide-by-zero for float division by zero
recovery [PR102515]
We've been using
-f{,no-}sanitize-recover=integer-divide-by-zero to decide on the float
-fsanitize=float-divide-by-zero instrumentation _abort suffix.
This patch fixes it to use -f{,no-}sanitize-recover=float-divide-by-zero
for it instead.
2021-10-01 Jakub Jelinek <jakub@redhat.com>
Richard Biener <rguenther@suse.de>
PR sanitizer/102515
gcc/c-family/
* c-ubsan.c (ubsan_instrument_division): Check the right
flag_sanitize_recover bit, depending on which sanitization
is done.
gcc/testsuite/
* c-c++-common/ubsan/float-div-by-zero-2.c: New test.
(cherry picked from commit 9c1a633d96926357155d4702b66f8a0ec856a81f)
prev parent reply other threads:[~2022-05-11 6:22 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
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 [this message]
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-hKdUoxHr3K@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: link
Be 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).