From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>,
Marek Polacek <polacek@redhat.com>,
Dodji Seketeli <dseketel@redhat.com>,
Konstantin Serebryany <konstantin.s.serebryany@gmail.com>,
Tobias Burnus <burnus@net-b.de>,
gcc-patches@gcc.gnu.org, rdsandiford@googlemail.com
Subject: Re: [PATCH] Add support for -fno-sanitize-recover and -fsanitize-undefined-trap-on-error (PR sanitizer/60275)
Date: Thu, 15 May 2014 10:34:00 -0000 [thread overview]
Message-ID: <20140515103357.GL10386@tucnak.redhat.com> (raw)
In-Reply-To: <87a9ajfi5r.fsf@talisman.default>
On Thu, May 15, 2014 at 11:30:40AM +0100, Richard Sandiford wrote:
> Jakub Jelinek <jakub@redhat.com> writes:
> > This patch adds two new options (compatible with clang) which allow
> > users to choose the behavior of undefined behavior sanitization.
> >
> > By default as before, all undefined behaviors (except for
> > __builtin_unreachable and missing return in C++) continue after reporting
> > which means that you can get lots of runtime errors from a single program
> > run and the exit code will not reflect the failure in that case.
> >
> > With this patch, one can use -fsanitize=undefined -fno-sanitize-recover,
> > which will report just the first undefined behavior and then exit with
> > non-zero code.
>
> Would it make sense for this to be the default for bootstrap-ubsan,
> so that the bootstrap fails on undefined behaviour?
Perhaps eventually, but is current bootstrap-ubsan really ubsan error free
on at least the major targets? I've made some efforts towards that goal on
x86_64-linux, but haven't tried bootstrap-ubsan recently.
Jakub
next prev parent reply other threads:[~2014-05-15 10:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 10:12 Jakub Jelinek
2014-04-23 8:14 ` Richard Biener
2014-05-15 10:30 ` Richard Sandiford
2014-05-15 10:34 ` Jakub Jelinek [this message]
2014-05-15 10:38 ` Marek Polacek
2014-05-15 12:42 ` Richard Sandiford
2014-05-15 12:47 ` Marek Polacek
2014-05-15 13:01 ` Richard Biener
2014-05-15 10:39 ` Ramana Radhakrishnan
2014-05-15 15:08 ` Marek Polacek
2014-05-15 15:16 ` Jakub Jelinek
2014-05-15 15:22 ` Marek Polacek
2014-05-15 18:32 ` Toon Moene
2014-05-15 18:37 ` Marek Polacek
2014-05-15 19:11 ` Jakub Jelinek
2014-05-15 19:20 ` Toon Moene
2014-05-15 19:27 ` Marek Polacek
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=20140515103357.GL10386@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=burnus@net-b.de \
--cc=dseketel@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=konstantin.s.serebryany@gmail.com \
--cc=polacek@redhat.com \
--cc=rdsandiford@googlemail.com \
--cc=rguenther@suse.de \
/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).