public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Oleg Endo <oleg.endo@t-online.de>
To: Bernd Schmidt <bschmidt@redhat.com>,
	Bernd Edlinger <bernd.edlinger@hotmail.de>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Andreas Krebbel <krebbel@linux.vnet.ibm.com>,
	Dominik Vogt	 <vogt@linux.vnet.ibm.com>,
	Kaz Kojima <kkojima@rr.iij4u.or.jp>
Subject: Re: [PATCH] Fix spec-options.c test case
Date: Mon, 02 May 2016 21:28:00 -0000	[thread overview]
Message-ID: <1462224483.31604.120.camel@t-online.de> (raw)
In-Reply-To: <57276071.1010206@redhat.com>

On Mon, 2016-05-02 at 16:13 +0200, Bernd Schmidt wrote:
> On 05/02/2016 03:43 PM, Bernd Edlinger wrote:
> > Yes, you are right.  Only the original use-case seems to be
> > sh-superh-elf specific.  But there are also spec strings
> > that are always available.  I think adding -DFOO to
> > "cpp_unique_options" will work on any target, and make the
> > test case even more useful.
> > 
> > 
> > So is the updated patch OK?
> 
> If that passes testing on non-sh, yes.

It seems that test case doesn't work on sh4-linux.  There's a new
failure:

https://gcc.gnu.org/ml/gcc-testresults/2016-05/msg00089.html

FAIL: gcc.dg/spec-options.c execution test


Cheers,
Oleg

  reply	other threads:[~2016-05-02 21:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-01  7:53 Bernd Edlinger
2016-05-02  8:31 ` Dominik Vogt
2016-05-02 10:26 ` Bernd Schmidt
2016-05-02 13:43   ` Bernd Edlinger
2016-05-02 14:13     ` Bernd Schmidt
2016-05-02 21:28       ` Oleg Endo [this message]
2016-05-03  0:05         ` Bernd Edlinger
2016-05-03  1:30           ` [gcc] " Kaz Kojima
2016-05-03  1:19         ` Kaz Kojima

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=1462224483.31604.120.camel@t-online.de \
    --to=oleg.endo@t-online.de \
    --cc=bernd.edlinger@hotmail.de \
    --cc=bschmidt@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kkojima@rr.iij4u.or.jp \
    --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).