From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
Mike Stump <mikestump@comcast.net>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Extend dg-{error,warning,message,bogus} line specification to allow relative line numbers
Date: Fri, 23 Sep 2016 15:02:00 -0000 [thread overview]
Message-ID: <20160923144311.GA22071@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160922200546.GH7282@tucnak.redhat.com>
On Thu, Sep 22, 2016 at 10:05:46PM +0200, Jakub Jelinek wrote:
> This is something I've been unhappy for a long time with, and finally got to
> write something for it.
> When some test expects more than one error or warning or message on the same
> source line, people have to use absolute line number on the dg-* directives
> that is not on the right line, as DejaGNU handles just . (current line, the
> default if the directive doesn't have all the arguments), 0 (no expected
> line) and <number> for absolute line number.
Great!
But could this patch be responsible with some dg-error related
test errors on s390x that are present with current HEAD? E.g.
(Sorry for the linebreaks that vim has inserted).
--
spawn -ignore SIGHUP /home/vogt/src/gcc/build-master/gcc/xgcc
-B/home/vogt/src/\
gcc/build-master/gcc/
/home/vogt/src/gcc/gcc/testsuite/gcc.target/s390/hotpatch\
-compile-1.c -fno-diagnostics-show-caret -fdiagnostics-color=never
-O3 -mzarch \
-mhotpatch=-1,0 -S -m64 -o hotpatch-compile-1.s^M
cc1: error: arguments to '-mhotpatch=n,m' should be non-negative
integers^M
compiler exited with status 1
output is:
cc1: error: arguments to '-mhotpatch=n,m' should be non-negative
integers^M
FAIL: gcc.target/s390/hotpatch-compile-1.c (test for errors, line
1)
FAIL: gcc.target/s390/hotpatch-compile-1.c (test for excess
errors)
Excess errors:
cc1: error: arguments to '-mhotpatch=n,m' should be non-negative
integers
--
So, the test expects an error:
/* { dg-error "arguments to .-mhotpatch=n,m. should be non-negative integers" "" { target *-*-* } 1 } */
but no longer matches the error that really occurs?
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
next prev parent reply other threads:[~2016-09-23 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 20:10 Jakub Jelinek
2016-09-23 1:21 ` Mike Stump
2016-09-23 15:02 ` Dominik Vogt [this message]
2016-09-23 15:05 ` Jakub Jelinek
2016-09-23 15:14 ` Dominik Vogt
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=20160923144311.GA22071@linux.vnet.ibm.com \
--to=vogt@linux.vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mikestump@comcast.net \
--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).