This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFC ThreadSanitizer testsuite
- From: Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>
- To: Yury Gribov <y dot gribov at samsung dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Konstantin Serebryany <kcc at gcc dot gnu dot org>, Jakub Jelinek <jakub at redhat dot com>, Viacheslav Garbuzov <v dot garbuzov at samsung dot com>, Evgeny Gavrin <e dot gavrin at samsung dot com>
- Date: Mon, 2 Dec 2013 14:21:11 +0400
- Subject: Re: RFC ThreadSanitizer testsuite
- Authentication-results: sourceware.org; auth=none
- References: <529C5D56 dot 6090209 at samsung dot com>
I'd be glad to have tsan tests in GCC.
At the very least we need to have a couple of sanity tests to make
sure tsan links and finds a trivial race.
The only mode in which my team can truly support tsan tests is when
they are verbatim copies of the upstream tests
and they are merged together with the rest of libsanitizer. (Which
implies that we use FileCheck or its clone)
Other mode may work too, but we will not own the tests (similarly, we
don't own the existing asan tests in GCC,
although if the tests need fixing during integrate we do it).
BTW, I am currently testing another libsanitizer merge.
--kcc
On Mon, Dec 2, 2013 at 2:13 PM, Yury Gribov <y.gribov@samsung.com> wrote:
> Hi all!
>
> Currently gcc has tests for AddressSanitizer and UBSanitizer. Do you think
> it would make sense to add support for ThreadSanitizer testing as well? If
> the answer is positive, we can work on dg infrastructure (tsan-dg.exp,
> tsan.exp) and initial set of tests. As for the latter: should we implement
> our own tests in gcc or simply copy from compiler-rt testsuite?
>
> -Y
>