public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bschmidt@redhat.com>
To: "Thomas Preud'homme" <thomas.preudhomme@foss.arm.com>,
	       "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
Cc: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>,
	gcc-patches@gcc.gnu.org,
	       Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
Subject: Re: [PATCH, testsuite] Fix g++.dg/pr67989.C test failure when running with -march or -mcpu
Date: Mon, 11 Jan 2016 15:57:00 -0000	[thread overview]
Message-ID: <5693D0DE.5090205@redhat.com> (raw)
In-Reply-To: <3386607.mP52vVFFoV@hardin.shanghai.arm.com>

On 01/08/2016 10:33 AM, Thomas Preud'homme wrote:
> 2016-01-08  Thomas Preud'homme  <thomas.preudhomme@arm.com>
>
>          * g++.dg/pr67989.C: Remove ARM-specific option.
>          * gcc.target/arm/pr67989.C: New file.

I checked some other arm tests and they have things like

/* { dg-skip-if "avoid conflicting multilib options" { *-*-* } { 
"-march=*" } { "-march=armv4t" } } */
/* { dg-skip-if "avoid conflicting multilib options" { *-*-* } { 
"-mthumb" } { "" } } */

Do you need the same in your testcase?


Bernd

  reply	other threads:[~2016-01-11 15:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05  7:37 Thomas Preud'homme
2016-01-05 10:47 ` Kyrill Tkachov
2016-01-05 10:52   ` Richard Earnshaw (lists)
2016-01-05 10:56     ` Kyrill Tkachov
2016-01-07  7:35   ` Thomas Preud'homme
2016-01-07  9:15     ` Kyrill Tkachov
2016-01-07 10:26       ` Richard Earnshaw (lists)
2016-01-08  9:33         ` Thomas Preud'homme
2016-01-11 15:57           ` Bernd Schmidt [this message]
2016-01-12  7:55             ` Thomas Preud'homme
2016-01-13 17:39               ` Bernd Schmidt
2016-01-18  3:33                 ` Thomas Preud'homme
2016-01-27  6:35                   ` Thomas Preud'homme
2016-01-27 20:04                     ` 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=5693D0DE.5090205@redhat.com \
    --to=bschmidt@redhat.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@foss.arm.com \
    --cc=ramana.radhakrishnan@arm.com \
    --cc=thomas.preudhomme@foss.arm.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).