From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: nickc@redhat.com
Cc: binutils@sourceware.org
Subject: New gas testsuite errors (was Re: [GAS] fix crash on erroneous directive)
Date: Fri, 29 Jul 2011 03:11:00 -0000 [thread overview]
Message-ID: <201107290036.p6T0ab45025285@ignucius.se.axis.com> (raw)
In-Reply-To: <4E3190E1.3020904@redhat.com> (message from Nick Clifton on Thu, 28 Jul 2011 17:40:01 +0100)
> Date: Thu, 28 Jul 2011 17:40:01 +0100
> From: Nick Clifton <nickc@redhat.com>
> >> You could define a symbol and then use to the right nop depending on the
> >> symbol's value.
> >
> > like this?
>
> Yes - although it turns out that there are other targets that have nops
> that take arguments, do not have a nop instruction at all, or do not
> generate dwarf2 debug information, so the test as you had it needed a
> little more tweaking. I have taken care of this however, and checked
> the result in.
Not sure why you didn't see this when you tested your changes
(for cris-elf but the target seems unimportant):
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-*-* } "
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.
brgds, H-P
next prev parent reply other threads:[~2011-07-29 0:37 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 ` Hans-Peter Nilsson [this message]
2011-07-29 12:10 ` New gas testsuite errors (was Re: [GAS] fix crash on erroneous directive) Nick Clifton
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=201107290036.p6T0ab45025285@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).