From: Bernd Schmidt <bschmidt@redhat.com>
To: Andreas Tobler <andreast-list@fgznet.ch>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] c/c++ asan tests for FreeBSD
Date: Mon, 30 Nov 2015 10:32:00 -0000 [thread overview]
Message-ID: <565C24BE.8020905@redhat.com> (raw)
In-Reply-To: <565B52BD.3020405@fgznet.ch>
On 11/29/2015 08:32 PM, Andreas Tobler wrote:
> Hi all,
>
> the attached patch prepares the testsuite, c and c++, for the upcoming
> ASAN support for FreeBSD (x86_64 first).
>
> I tested the patch on CentOS7.1 x86_64 and on FreeBSD x86_64.
> Results can be seen on the list.
>
> Is this ok for trunk?
>
> -/* { dg-do run { target { *-*-linux* } } } */
> +/* { dg-do run { target { *-*-linux* *-*-freebsd* } } } */
I see a patch from you to add asan support to x86 freebsd, but what
about other architectures?
Bernd
next prev parent reply other threads:[~2015-11-30 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 20:03 Andreas Tobler
2015-11-29 22:10 ` Andreas Tobler
2015-11-30 10:32 ` Bernd Schmidt [this message]
2015-11-30 12:12 ` Andreas Tobler
2015-11-30 16:22 ` Bernd Schmidt
2015-11-30 16:33 ` Jakub Jelinek
2015-11-30 20:18 ` Andreas Tobler
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=565C24BE.8020905@redhat.com \
--to=bschmidt@redhat.com \
--cc=andreast-list@fgznet.ch \
--cc=gcc-patches@gcc.gnu.org \
/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).