public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: vogt@linux.vnet.ibm.com, gcc-patches@gcc.gnu.org,
	       Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] Run tests only if the machine supports the instruction set.
Date: Mon, 19 Dec 2016 17:01:00 -0000	[thread overview]
Message-ID: <20161219170021.GW21933@tucnak> (raw)
In-Reply-To: <20161219165040.GA15966@linux.vnet.ibm.com>

On Mon, Dec 19, 2016 at 05:50:40PM +0100, Dominik Vogt wrote:
> 	* config/s390/s390-c.c (s390_cpu_cpp_builtins_internal): Define
> 	__S390_ARCH_LEVEL__.
> gcc/testsuite/ChangeLog-setmem
> 
> 	* gcc.target/s390/md/setmem_long-1.c: Use "runnable".
> 	* gcc.target/s390/md/rXsbg_mode_sXl.c: Likewise.
> 	* gcc.target/s390/md/andc-splitter-1.c: Likewise.
> 	* gcc.target/s390/md/andc-splitter-2.c: Likewise.
> 	* lib/gcc-dg.exp (gcc-dg-runtest): Export torture_current_flags.
> 	* gcc.target/s390/s390.exp: Import torture_current_flags.
> 	(check_effective_target_runnable): New.

Unless you want to add support for all targets in the runnable
effective target, I think it would be better to call it less generically,
s390_runnable or similar.

	Jakub

  reply	other threads:[~2016-12-19 17:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19 14:32 Dominik Vogt
2016-12-19 16:51 ` [PATCH v2] " Dominik Vogt
2016-12-19 17:01   ` Jakub Jelinek [this message]
2016-12-20 10:33     ` Dominik Vogt
2016-12-20 10:38       ` Jakub Jelinek
2016-12-20 14:16         ` [PATCH v3] " Dominik Vogt
2016-12-20 20:14           ` Mike Stump
2016-12-20 21:29             ` [PATCH v4] " Dominik Vogt
2016-12-20 23:59               ` Jakub Jelinek
2016-12-21 10:00                 ` Dominik Vogt
2016-12-22 15:18               ` Andreas Krebbel

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=20161219170021.GW21933@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=krebbel@linux.vnet.ibm.com \
    --cc=vogt@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).