public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: janis_johnson@mentor.com
Cc: gcc-patches@gcc.gnu.org, rearnshaw@cambridge.arm.com
Subject: Re: PING: gcc.target/arm: skip 5 tests for flag conflicts
Date: Wed, 16 Jan 2013 13:35:00 -0000	[thread overview]
Message-ID: <871udl5k5c.fsf@redhat.com> (raw)

Hi Janis,

> Back in September I submitted a patch to fix five ARM tests in
>  <http://gcc.gnu.org/ml/gcc-patches/2012-09/msg01515.html>.
> You responded in < http://gcc.gnu.org/ml/gcc-patches/2012-10/msg00972.html>
> and I answered your questions in a reply.

I believe that Richard's main point was that the skips that you were
adding to the tests meant that they would not be run for valid
command line options.

Eg:

  Index: gcc.target/arm/pr53187.c
  ===================================================================
  --- gcc.target/arm/pr53187.c	(revision 191502)
  +++ gcc.target/arm/pr53187.c	(working copy)
  @@ -1,5 +1,6 @@
    /* PR target/53187 */
    /* { dg-do compile } */
  + /* { dg-skip-if "do not override -march" { *-*-* } { "-march=*" } { "-march=armv7-a" } } */
    /* { dg-options "-march=armv7-a -mfloat-abi=hard -O2" } */

With your patch applied this test will be skipped when, eg,
-march=armv7-r is specified as the multilib selector.  Or in fact any
-march that is not armv7-a, even though, for many of these, the test
will successfully compile.

Given that there are more compatible architectures than incompatible
ones, I think that it would be better to allow the test by default and
only exclude when necessary.  Eg:

    /* PR target/53187 */
    /* { dg-do compile } */
  + /* { dg-skip-if "incompatible -march" { *-*-* } { "-march=armv6s-m" "-march=armv6-m" } { "" } } */
    /* { dg-options "-march=armv7-a -mfloat-abi=hard -O2" } */

Cheers
  Nick

             reply	other threads:[~2013-01-16 13:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 13:35 Nick Clifton [this message]
2013-01-16 23:47 ` Janis Johnson
2013-01-17 15:04   ` nick clifton
  -- strict thread matches above, loose matches on Subject: below --
2013-01-14 21:21 Janis Johnson

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=871udl5k5c.fsf@redhat.com \
    --to=nickc@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=janis_johnson@mentor.com \
    --cc=rearnshaw@cambridge.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).