On Thu, 25 Jul 2013, Joseph S. Myers wrote:
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.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57324
(that is using llvm's sanitizer)
and for a first patch (unreviewed):
http://gcc.gnu.org/ml/gcc-patches/2013-06/msg01466.html
(started at http://gcc.gnu.org/ml/gcc-patches/2013-05/msg01402.html )
--
Marc Glisse
