From: Eric Botcazou <ebotcazou@adacore.com>
To: janisjo@codesourcery.com
Cc: gcc-patches@gcc.gnu.org
Subject: Re: testsuite] clean up convoluted dg-final directive in vect-multitypes-12.c
Date: Wed, 23 Jan 2013 22:53:00 -0000 [thread overview]
Message-ID: <2987551.qUaChJ0c29@polaris> (raw)
In-Reply-To: <50F980CE.6030609@mentor.com>
> Test gcc.dg/vect/vect-multitypes uses Tcl conditions within a dg-final
> directive, which is something that DejaGnu handles but we strive not to
> do. It's now possible to use supported constructs to get the same
> result, so I've cleaned up the test and checked it in as obvious. I'm
> fixing this particular test because I want to add an xfail but want to
> keep that change separate from the cleanup.
Something doesn't work anymore for SPARC though:
ERROR: gcc.dg/vect/vect-multitypes-12.c: error executing dg-final: bad index
"18-1": must be integer or end?-integer?
UNRESOLVED: gcc.dg/vect/vect-multitypes-12.c: error executing dg-final: bad
index "18-1": must be integer or end?-integer?
ERROR: gcc.dg/vect/vect-multitypes-12.c -flto: error executing dg-final: bad
index "18-1": must be integer or end?-integer?
UNRESOLVED: gcc.dg/vect/vect-multitypes-12.c -flto: error executing dg-final:
bad index "18-1": must be integer or end?-integer?
--
Eric Botcazou
next prev parent reply other threads:[~2013-01-23 22:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 17:02 Janis Johnson
2013-01-23 22:53 ` Eric Botcazou [this message]
2013-01-23 23:36 ` Janis Johnson
2013-01-24 0:58 ` Eric Botcazou
2013-01-24 1:02 ` Janis Johnson
2013-01-24 9:16 ` Andreas Schwab
2013-01-30 8:28 ` Jakub Jelinek
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=2987551.qUaChJ0c29@polaris \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=janisjo@codesourcery.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).