From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Jason Merrill <jason@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Richard Biener <richard.guenther@gmail.com>
Subject: Re: [PATCH RFA] ubsan: default to trap on unreachable at -O0 and -Og [PR104642]
Date: Thu, 16 Jun 2022 22:53:20 +0200 [thread overview]
Message-ID: <YquYQCHUCkXJft0f@tucnak> (raw)
In-Reply-To: <CAH6eHdR9h21GbGS97P2bfaz2Xd4K9585hJ1VZ-v5q6CT-ULYmA@mail.gmail.com>
On Thu, Jun 16, 2022 at 09:32:02PM +0100, Jonathan Wakely wrote:
> It looks like clang has addressed this deficiency now:
>
> https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html#usage
Thanks, will study how it works tomorrow.
Jakub
next prev parent reply other threads:[~2022-06-16 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 19:53 Jason Merrill
2022-06-14 11:44 ` Jakub Jelinek
2022-06-15 20:38 ` Jason Merrill
2022-06-16 13:14 ` Jakub Jelinek
2022-06-20 20:30 ` Jason Merrill
2022-06-21 11:17 ` Jakub Jelinek
2022-06-22 3:59 ` Jason Merrill
2022-06-22 8:05 ` Jakub Jelinek
2022-06-16 20:32 ` Jonathan Wakely
2022-06-16 20:53 ` Jakub Jelinek [this message]
2022-06-17 15:34 ` [PATCH] ubsan: Add -fsanitize-trap= support Jakub Jelinek
2022-06-17 18:21 ` Jason Merrill
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=YquYQCHUCkXJft0f@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jwakely.gcc@gmail.com \
--cc=richard.guenther@gmail.com \
/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).