From: James E Wilson <wilson@specifixinc.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] ia64: certain symbol names were unusable
Date: Thu, 17 Feb 2005 03:22:00 -0000 [thread overview]
Message-ID: <1108584688.27293.3.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <s20c8f76.003@emea1-mh.id2.novell.com>
On Fri, 2005-02-11 at 02:57, Jan Beulich wrote:
> * config/tc-ia64.c (ia64_parse_name): Don't advance 'name' when
> parsing inN, locN, outN. ...
FYI This is the in-loc-out patch. I haven't seen this one get applied
yet. I approved it Friday last week.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2005-02-16 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 15:54 Jan Beulich
2005-02-17 3:22 ` James E Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-17 15:37 Jan Beulich
[not found] <s20c8f76.004@emea1-mh.id2.novell.com>
2005-02-11 20:41 ` James E Wilson
2005-02-08 17:05 Jan Beulich
2005-02-11 3:46 ` 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=1108584688.27293.3.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).