From: Nick Clifton <nickc@redhat.com>
To: clm@cm00re.com
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Additional TC_EQUAL_IN_INSN check
Date: Fri, 18 Feb 2005 21:41:00 -0000 [thread overview]
Message-ID: <4215FF5D.8040208@redhat.com> (raw)
In-Reply-To: <200502171836.j1HIaXgg006973@mx1.redhat.com>
Hi Catherine,
> I don't think passing an extra argument is a big deal. If s is available,
> why not use it instead of deducing it?
Well my point was: "why make an unnecessary change ?"
> It turns out that the only port
> (other than the one I'm working on) which uses this macro is the hppa and
> the hppa port doesn't look at the string. I've reworked the patch to pass s
> and not input_line_pointer to the TC_EQUAL_IN_INSN macro and also to use
> only one invocation of the macro as you suggested. Okay to install, now?
Yes, with the proviso that you fix the documentation as Alan suggested.
> * read.c (read_a_source_file): Check TC_EQUAL_IN_INSN if c is '='.
> * doc/internals.texi (TC_EQUAL_IN_INSN): Pass current string instead of
> input_line_pointer.
Approved.
> If you define this macro, it should return nonzero if the instruction is
> permitted to contain an @kbd{=} character. GAS will call it with two
> arguments, the character before the @kbd{=} character, and the value of
> ! @code{s} at that point. GAS uses this macro to decide if a
> @kbd{=} is an assignment or an instruction.
How about "and the string that follows after the equals sign" ?
Cheers
Nick
next parent reply other threads:[~2005-02-18 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200502171836.j1HIaXgg006973@mx1.redhat.com>
2005-02-18 21:41 ` Nick Clifton [this message]
2005-02-18 21:43 ` Catherine Moore
[not found] <200502181605.j1IG5t7e028779@mx1.redhat.com>
2005-02-18 22:14 ` Nick Clifton
[not found] <200502151337.j1FDb4u2012330@mx3.redhat.com>
2005-02-16 17:54 ` Nick Clifton
2005-02-17 21:34 ` Catherine Moore
[not found] ` <20050217183642.EVRM13037.imta01ps.mx.bigpond.com@psmam02.bigpond.com>
2005-02-18 12:36 ` Alan Modra
2005-02-15 18:10 Catherine Moore
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=4215FF5D.8040208@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=clm@cm00re.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).