From: James E Wilson <wilson@specifixinc.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] Re: ia64: @ not allowed to start symbol?
Date: Fri, 11 Feb 2005 07:05:00 -0000 [thread overview]
Message-ID: <1108084207.24473.136.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <s208e831.072@emea1-mh.id2.novell.com>
On Tue, 2005-02-08 at 08:27, Jan Beulich wrote:
> * config/tc-ia64.h (LEX_AT): Include LEX_BEGIN_NAME.
> (LEX_QM): Likewise.
> ...
OK.
I found the use of "pc" as a parameter name in ia64_parse_name a little
confusing, as every time I see pc I think program counter, but this has
nothing to do with an object file address or the program counter. I
think nextchar or nextcharP as used in some of the other target ports is
a better parameter name.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2005-02-11 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 20:05 Jan Beulich
2005-02-11 7:05 ` James E Wilson [this message]
2005-02-14 19:45 Jan Beulich
2005-02-15 0:01 ` James E Wilson
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=1108084207.24473.136.camel@aretha.corp.specifixinc.com \
--to=wilson@specifixinc.com \
--cc=JBeulich@novell.com \
--cc=binutils@sources.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).