From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: wschmidt@linux.vnet.ibm.com (Bill Schmidt)
Cc: m.ostapenko@samsung.com (Maxim Ostapenko),
gcc@gcc.gnu.org, jakub@redhat.com (Jakub Jelinek)
Subject: Re: -fsanitize=thread support on ppc64
Date: Mon, 23 Jan 2017 15:10:00 -0000 [thread overview]
Message-ID: <20170123151002.060C510B914@oc8523832656.ibm.com> (raw)
In-Reply-To: <0A781485-6F99-47E6-9563-14EDB0568CF9@linux.vnet.ibm.com> from "Bill Schmidt" at Jan 23, 2017 08:42:06 AM
Bill Schmidt wrote:
> On Jan 23, 2017, at 8:32 AM, Jakub Jelinek <jakub@redhat.com> wrote:
> >
> > Another question is, it seems upstream has s390{,x}-*-linux* support for
> > asan/ubsan, does that work? In that case we should add it to configure.tgt
> > too (similarly to the sparc*-*-linux* entry).
>
> CCing Uli for the s390 question.
Asan support was added just recently to LLVM for s390x-linux. However,
I'm not sure it will work out-of-the-box on GCC, since we haven't done any
back-end work to enable it. Also, LLVM is 64-bit only, so there probably
would have to be extra work in the libraries to enable 31-bit mode.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2017-01-23 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170123113432epcas1p2951bfbb1968a143a14b9c54475ff3527@epcas1p2.samsung.com>
2017-01-23 11:34 ` Jakub Jelinek
2017-01-23 12:54 ` Maxim Ostapenko
2017-01-23 14:22 ` Bill Schmidt
2017-01-23 14:32 ` Jakub Jelinek
2017-01-23 14:41 ` Bill Schmidt
2017-01-23 15:10 ` Ulrich Weigand [this message]
2017-01-23 15:27 ` Jakub Jelinek
2017-01-23 14:44 ` Bill Schmidt
2017-01-23 14:47 ` Jakub Jelinek
2017-01-23 14:48 ` Bill Schmidt
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=20170123151002.060C510B914@oc8523832656.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=m.ostapenko@samsung.com \
--cc=wschmidt@linux.vnet.ibm.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).