From: Nathan Sidwell <nathan@codesourcery.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Andreas Schwab <schwab@redhat.com>, binutils <binutils@sourceware.org>
Subject: Re: [GAS] fix crash on erroneous directive
Date: Thu, 28 Jul 2011 16:58:00 -0000 [thread overview]
Message-ID: <4E319163.6070606@codesourcery.com> (raw)
In-Reply-To: <4E3190E1.3020904@redhat.com>
On 07/28/11 17:40, Nick Clifton wrote:
> 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.
thanks!
nathan
--
Nathan Sidwell
next prev parent reply other threads:[~2011-07-28 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 12:33 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 [this message]
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
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=4E319163.6070606@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=schwab@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).