This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Add support for -fno-sanitize-recover and -fsanitize-undefined-trap-on-error (PR sanitizer/60275)
- From: Marek Polacek <polacek at redhat dot com>
- To: Toon Moene <toon at moene dot org>
- Cc: ramrad01 at arm dot com, Jakub Jelinek <jakub at redhat dot com>, Richard Biener <rguenther at suse dot de>, Dodji Seketeli <dseketel at redhat dot com>, Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>, Tobias Burnus <burnus at net-b dot de>, gcc-patches <gcc-patches at gcc dot gnu dot org>, Richard Sandiford <rdsandiford at googlemail dot com>
- Date: Thu, 15 May 2014 20:37:07 +0200
- Subject: Re: [PATCH] Add support for -fno-sanitize-recover and -fsanitize-undefined-trap-on-error (PR sanitizer/60275)
- Authentication-results: sourceware.org; auth=none
- References: <20140415101156 dot GB1817 at tucnak dot redhat dot com> <87a9ajfi5r dot fsf at talisman dot default> <20140515103357 dot GL10386 at tucnak dot redhat dot com> <CAJA7tRb=HJb3srtHqb3QBp03ujyBWkHmjQWU0ey8F_qN99gzng at mail dot gmail dot com> <20140515150810 dot GD8173 at redhat dot com> <53750844 dot 4030205 at moene dot org>
On Thu, May 15, 2014 at 08:32:36PM +0200, Toon Moene wrote:
> On 05/15/2014 05:08 PM, Marek Polacek wrote:
>
> >On Thu, May 15, 2014 at 11:39:26AM +0100, Ramana Radhakrishnan wrote:
> >>What's the overhead with bootstrap-ubsan ?
> >
> >I timed normal bootstrap and bootstrap-ubsan on x86_64, 24 cores,
> >Intel(R) Xeon(R) CPU X5670 @ 2.93GHz (aka cfarm 20) and the results:
> >
> >--enable-languages=all
> >
> >real 35m10.419s
> >user 204m5.613s
> >sys 6m15.615s
> >
> >--enable-languages=all --with-build-config=bootstrap-ubsan
> >
> >real 71m39.338s
> >user 347m53.409s
> >sys 7m44.281s
>
> And don't underestimate the *usefulness* of this - if you don't have the
> resources to do a ubsan bootstrap, download mine from last night
> (x86_64-linux-gnu): http://moene.org/~toon/gcc-tests.log.gz
>
> [ I hope there is a way to discard color codings when writing error messages
> to a file, ugh ]
Sure, -fdiagnostics-color=auto "means to use color only when the
standard error is a terminal", or -fdiagnostics-color=never to turn it
off completely (testsuite uses the latter).
Marek