From: "Terry Guo" <terry.guo@arm.com>
To: <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH, testsuite] Avoid architecture options conflict for case pr42894.c
Date: Tue, 30 Aug 2011 09:12:00 -0000 [thread overview]
Message-ID: <000001cc65ec$8bc3e460$a34bad20$@guo@arm.com> (raw)
In-Reply-To:
Ping.
BR,
Terry
> -----Original Message-----
> From: Terry Guo [mailto:terry.guo@arm.com]
> Sent: Thursday, August 25, 2011 7:46 PM
> To: 'gcc-patches@gcc.gnu.org'
> Subject: [PATCH, testsuite] Avoid architecture options conflict for
> case pr42894.c
>
> Hello,
>
> I think it is useful to run this case for newer arm targets. So the
> patch intends to skip the warning of architecture conflicts. Is it ok
> to commit to trunk?
>
> BR,
> Terry
>
> gcc/testsuite/ChangeLog:
>
> 2011-08-25 Terry Guo <terry.guo@arm.com>
>
> * gcc.dg/tls/pr42894.c: Add dg-prune-output to skip
> architecture conflict.
>
>
> diff --git a/gcc/testsuite/gcc.dg/tls/pr42894.c
> b/gcc/testsuite/gcc.dg/tls/pr42894.c
> index c3bd76c..cda6719 100644
> --- a/gcc/testsuite/gcc.dg/tls/pr42894.c
> +++ b/gcc/testsuite/gcc.dg/tls/pr42894.c
> @@ -2,6 +2,7 @@
> /* { dg-do compile } */
> /* { dg-options "-march=armv5te -mthumb" { target arm*-*-* } } */
> /* { dg-require-effective-target tls } */
> +/* { dg-prune-output "switch .* conflicts with" } */
>
> extern __thread int t;
next reply other threads:[~2011-08-30 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 9:12 Terry Guo [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-09 5:14 Terry Guo
2011-08-25 12:35 Terry Guo
2011-09-09 9:17 ` Richard Earnshaw
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='000001cc65ec$8bc3e460$a34bad20$@guo@arm.com' \
--to=terry.guo@arm.com \
--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).