From: Nick Clifton <nickc@redhat.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: binutils@sourceware.org
Subject: Re: New gas testsuite errors (was Re: [GAS] fix crash on erroneous directive)
Date: Fri, 29 Jul 2011 12:10:00 -0000 [thread overview]
Message-ID: <4E32939F.60804@redhat.com> (raw)
In-Reply-To: <201107290036.p6T0ab45025285@ignucius.se.axis.com>
Hi Hans-Peter,
> Not sure why you didn't see this when you tested your changes
>
> Running /tmp/hpautotest-binutils/bsrc/src/gas/testsuite/gas/elf/elf.exp ...
> ERROR: gas/elf/warn-2.s: unknown dg option: dg-skip-if 2 {DWARF2 output not supported} { mcore-*-* mn10*-*-* moxie-*-* v850-*-* } for " dg-skip-if 2 "DWARF2 output not supported" { mcore-*-* mn10*-*-* moxie-*-* v850-*-* } "
Snafu - I use a script to parse for testsuite regressions. It was
looking for new FAIL messages, but it omitted to check for new ERROR
messages. I have fixed this now.
> There's no dg-skip-if in binutils (and none in dejagnu-1.4.4.),
> that's just in the gcc testsuite... No obvious patch,
> unfortunately.
I have fixed warn-2.s so that the test for the warning message is
xfailed on those targets that will not produce it, and the nop
instruction for the OpenRisc targets is encoded as "l.no 0". With these
changes the test now works for all of the targets that I checked.
Cheers
Nick
prev parent reply other threads:[~2011-07-29 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 12:33 [GAS] fix crash on erroneous directive Nathan Sidwell
2011-07-27 13:20 ` Andreas Schwab
2011-07-27 14:05 ` Nathan Sidwell
2011-07-27 16:26 ` Andreas Schwab
2011-07-28 14:03 ` Nathan Sidwell
2011-07-28 16:42 ` Nick Clifton
2011-07-28 16:58 ` Nathan Sidwell
2011-07-29 3:11 ` New gas testsuite errors (was Re: [GAS] fix crash on erroneous directive) Hans-Peter Nilsson
2011-07-29 12:10 ` Nick Clifton [this message]
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=4E32939F.60804@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=hans-peter.nilsson@axis.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).