From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: Jeff Law <law@redhat.com>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
gcc-patches@gcc.gnu.org,
Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Subject: Re: [PATCH] Clean up tests where a later dg-do completely overrides another.
Date: Mon, 02 May 2016 16:24:00 -0000 [thread overview]
Message-ID: <20160502162413.GA5098@linux.vnet.ibm.com> (raw)
In-Reply-To: <b0d3e0ce-7edd-6f7b-7e42-5a7518806ea9@redhat.com>
On Mon, May 02, 2016 at 09:29:50AM -0600, Jeff Law wrote:
> On 04/29/2016 05:56 PM, Dominik Vogt wrote:
> > ...
> >Maybe a comment should be added to the test case
> >
> > /* If this test is *run* (not just compiled) and therefore fails
> > on non sh*-targets, this is because of a bug older DejaGnu
> > versions. This is fixed with DejaGnu-1.6. */
> I think we have a couple issues now that are resolved if we step
> forward to a newer version of dejagnu.
>
> Given dejagnu-1.6 was recently released, should we just bite the
> bullet and ask everyone to step forward?
I'm all for that. I've recently added s390 test cases that
require Dejagnu 1.6. Apart from the discussed problem with
spec-options.c, there are a number of Power (and some other
target) test cases that do not work properly with older Dejagnu
version but would finally work (read: actually test something) if
the new version were required.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
next prev parent reply other threads:[~2016-05-02 16:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 7:50 Dominik Vogt
2016-04-27 8:52 ` Bernd Schmidt
2016-04-29 9:24 ` Andreas Krebbel
2016-04-29 20:03 ` Rainer Orth
2016-04-29 23:56 ` Dominik Vogt
2016-05-02 15:30 ` Jeff Law
2016-05-02 16:24 ` Dominik Vogt [this message]
2016-05-18 21:59 ` Jeff Law
2016-05-26 4:18 ` Mike Stump
2016-05-28 20:47 ` Gerald Pfeifer
2016-04-30 10:55 Bernd Edlinger
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=20160502162413.GA5098@linux.vnet.ibm.com \
--to=vogt@linux.vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=krebbel@linux.vnet.ibm.com \
--cc=law@redhat.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).