This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Request to merge Undefined Behavior Sanitizer in
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Marek Polacek <polacek at redhat dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Jakub Jelinek <jakub at redhat dot com>, Jeff Law <law at redhat dot com>, Jason Merrill <jason at redhat dot com>
- Date: Thu, 25 Jul 2013 22:40:22 +0000
- Subject: Re: Request to merge Undefined Behavior Sanitizer in
- References: <20130725153227 dot GC32538 at redhat dot com>
On Thu, 25 Jul 2013, Marek Polacek wrote:
> So far it sanitizes division-by-zeros, shifts and
> __builtin_unreachable calls. This is of course far from being
> complete; I intend to write more features during this 4.9 stage.
Such as everything needed for it to replace -ftrapv (for -ftrapv to become
an alias for an appropriate subset of this option)?
What happens if you bootstrap with this enabled - do whatever failures
appear look like genuine bugs? Running the testsuite with a compiler
built with this option? Running the testsuite with this option used when
compiling all these tests. I guess that initially a bootstrap with this
option may fail because of existing bugs, and so the other tests mentioned
can't yet be run - but using this option on GCC itself, and making sure
that as far as possible it doesn't break compiling things or change
diagnostics generated at compile time, seem like good goals.
--
Joseph S. Myers
joseph@codesourcery.com