From: Konstantin Serebryany <konstantin.s.serebryany@gmail.com>
To: Wei Mi <wmi@google.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
David Li <davidxl@google.com>,
Diego Novillo <dnovillo@google.com>,
Jakub Jelinek <jakub@redhat.com>,
Kostya Serebryany <kcc@google.com>,
Dodji Seketeli <dseketel@redhat.com>
Subject: Re: [PATCH] asan unit tests from llvm lit-test
Date: Wed, 28 Nov 2012 10:10:00 -0000 [thread overview]
Message-ID: <CAGQ9bdxmMfsyas_+P9ZwNSPbAp3kXE7Rg7fetfCUdLo3+4gGcw@mail.gmail.com> (raw)
In-Reply-To: <CA+4CFy5jX04sXyvVNWx=jwch5PP6JE0amCK3XGntqKKNjr7SEQ@mail.gmail.com>
I'd like to understand our long-term strategy wrt the asan/tsan tests in gcc.
Most of the tests we have today are not specific to the compiler and
so can potentially be used with any compiler.
The problem is the testing harness (FileCheck/gtest vs dejagnu).
I understand that using alien testing harnesses in the gcc tree might
be unacceptable,
but the other choice is doubled maintenance burden for tests.
I suggest we discuss this general problem first.
--kcc
On Wed, Nov 28, 2012 at 1:15 PM, Wei Mi <wmi@google.com> wrote:
> Hi,
>
> I try to migrate the left asan lit-tests from llvm (class3). This is a
> preliminary version patch. Please forgive it has many mistakes.
>
> A known problems: I hardcoded -m32 in (set link_flags
> "[asan_link_flags [get_multilibs -m32]] $link_flags") in
> gcc/testsuite/lib/asan-dg.exp to make 32 bit library path included in
> ld_library_path. I don't know the elegant way to fix it.
>
> Thanks,
> Wei.
>
> gcc/testsuite/
> 2012-11-28 Wei Mi <wmi@google.com>
>
> * gcc.dg/asan/asan.exp: Case by case processing for some
> special testcases.
> * g++.dg/asan/asan.exp: Likewise.
> * lib/asan-dg.exp: Likewise.
> * g++.dg/asan/linux: New, migrate from llvm asan lit-test.
> * g++.dg/asan/linux/interception-test-1.C: Likewise.
> * g++.dg/asan/linux/interception-failure-test-1.C: Likewise.
> * g++.dg/asan/linux/interception-malloc-test-1.C: Likewise.
> * g++.dg/asan/Helpers: Likewise.
> * g++.dg/asan/Helpers/initialization-blacklist-1.tmp: Likewise.
> * g++.dg/asan/Helpers/initialization-blacklist-extra-1.C: Likewise.
> * g++.dg/asan/deep-thread-stack-1.C: Likewise.
> * g++.dg/asan/shared-lib-test-1.C: Likewise.
> * g++.dg/asan/deep-stack-uaf-1.C: Likewise.
> * g++.dg/asan/on-error-callback-1.C: Likewise.
> * g++.dg/asan/initialization-blacklist-1.C: Likewise.
> * g++.dg/asan/initialization-nobug-1.C: Likewise.
> * g++.dg/asan/large-func-test-1.C: Likewise.
> * g++.dg/asan/SharedLibs: Likewise.
> * g++.dg/asan/SharedLibs/dlclose-test-1-so.C: Likewise.
> * g++.dg/asan/SharedLibs/shared-lib-test-1-so.C: Likewise.
> * g++.dg/asan/dlclose-test-1.C: Likewise.
> * g++.dg/asan/malloc-hook-1.C: Likewise.
> * g++.dg/asan/symbolize-callback-1.C: Likewise.
> * g++.dg/asan/default-options-1.C: Likewise.
> * g++.dg/asan/deep-tail-call-1.C: Likewise.
> * c-c++-common/asan/linux: Likewise.
> * c-c++-common/asan/linux/initialization-bug-any-order-1.c: Likewise.
> * c-c++-common/asan/linux/rlimit-mmap-test-1.c: Likewise.
> * c-c++-common/asan/linux/swapcontext-test-1.c: Likewise.
> * c-c++-common/asan/linux/clone-test-1.c: Likewise.
> * c-c++-common/asan/sleep-before-dying-1.c: Likewise.
> * c-c++-common/asan/Helpers: Likewise.
> * c-c++-common/asan/Helpers/blacklist-extra-1.c: Likewise.
> * c-c++-common/asan/Helpers/interface_symbols.sh: Likewise.
> * c-c++-common/asan/Helpers/initialization-bug-extra-1.c: Likewise.
> * c-c++-common/asan/Helpers/blacklist-1.tmp: Likewise.
> * c-c++-common/asan/interface-symbols-1.c: Likewise.
> * c-c++-common/asan/strip-path-prefix-1.c: Likewise.
> * c-c++-common/asan/force-inline-opt0-1.c: Likewise.
> * c-c++-common/asan/null-deref-1.c: Likewise.
> * c-c++-common/asan/global-overflow-1.c: Likewise.
> * c-c++-common/asan/initialization-bug-1.c: Likewise.
> * c-c++-common/asan/strncpy-overflow-1.c: Likewise.
> * c-c++-common/asan/stack-overflow-1.c: Likewise.
> * c-c++-common/asan/blacklist-1.c: Likewise.
> * c-c++-common/asan/use-after-free-1.c: Likewise.
> * c-c++-common/asan/sanity-check-pure-c-1.c: Likewise.
> * c-c++-common/asan/stack-use-after-return-1.c: Likewise.
> * c-c++-common/asan/heap-overflow-1.c: Likewise.
next prev parent reply other threads:[~2012-11-28 10:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 9:15 Wei Mi
2012-11-28 10:10 ` Konstantin Serebryany [this message]
2012-11-28 10:25 ` Jakub Jelinek
2012-11-28 10:41 ` Konstantin Serebryany
2012-11-28 11:03 ` Jakub Jelinek
2012-11-28 11:14 ` Konstantin Serebryany
2012-11-29 20:59 ` [PATCH] asan_test.cc from llvm Jakub Jelinek
2012-11-30 9:35 ` Konstantin Serebryany
2012-11-30 10:22 ` Jakub Jelinek
2012-11-30 10:55 ` Konstantin Serebryany
2012-11-30 14:52 ` Jakub Jelinek
2012-11-30 16:06 ` Jakub Jelinek
[not found] ` <CAKOQZ8y70goUL91pQJt_S=8W+Dn5VTZ5oRphvGuFwMMh41mkLg@mail.gmail.com>
2012-11-30 16:34 ` Jakub Jelinek
2012-12-03 7:07 ` Konstantin Serebryany
2012-12-03 9:18 ` Jakub Jelinek
2012-12-03 9:52 ` Konstantin Serebryany
2012-12-03 11:05 ` Jakub Jelinek
2012-12-03 11:42 ` Konstantin Serebryany
2012-11-28 11:25 ` [PATCH] asan unit tests from llvm lit-test Jakub Jelinek
2012-11-28 11:39 ` Konstantin Serebryany
2012-11-28 10:14 ` Jakub Jelinek
2012-11-30 21:05 ` Wei Mi
2012-12-03 7:16 ` Konstantin Serebryany
2012-12-03 11:01 ` Jakub Jelinek
2012-12-03 18:33 ` Wei Mi
2012-12-03 18:49 ` Konstantin Serebryany
2012-12-03 19:44 ` Jakub Jelinek
2012-12-03 19:09 ` Mike Stump
2012-12-03 19:37 ` Jakub Jelinek
2012-12-03 19:50 ` Mike Stump
[not found] ` <CAN=P9pgjjq66KS2DVkuOSeH2ejQPDcyKhwz5MdKyE3RB64E=xw@mail.gmail.com>
2012-12-04 7:34 ` Jakub Jelinek
2012-12-04 18:01 ` Wei Mi
2012-12-05 12:29 ` [PATCH] asan unit tests from llvm lit-test incremental changes Jakub Jelinek
2012-12-12 21:32 ` Dodji Seketeli
2012-12-12 21:31 ` Jakub Jelinek
2012-12-13 7:44 ` Konstantin Serebryany
2012-12-13 8:37 ` Jakub Jelinek
2012-12-13 10:23 ` Konstantin Serebryany
2012-12-13 15:22 ` Jakub Jelinek
2012-12-05 23:29 ` [asan] Fix up dg-set-target-env-var Jakub Jelinek
2012-12-06 0:23 ` Mike Stump
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=CAGQ9bdxmMfsyas_+P9ZwNSPbAp3kXE7Rg7fetfCUdLo3+4gGcw@mail.gmail.com \
--to=konstantin.s.serebryany@gmail.com \
--cc=davidxl@google.com \
--cc=dnovillo@google.com \
--cc=dseketel@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kcc@google.com \
--cc=wmi@google.com \
/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).