public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: James E Wilson <wilson@specifixinc.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: binutils@sources.redhat.com
Subject: Re: open ia64 issues
Date: Thu, 17 Feb 2005 05:03:00 -0000	[thread overview]
Message-ID: <1108599702.27293.101.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <s211b7f3.065@emea1-mh.id2.novell.com>

On Tue, 2005-02-15 at 00:51, Jan Beulich wrote:
> OK, then I'll put this on my mid-term todo list.

You could always document bugs by filing them into bugzilla.  Though
realistically, if you aren't fixing these problems yourself, you will
have a long wait before anyone else does.

> It could reject reserved symbols, but as I said above that's not how ias appears to behave;

So that's another case where IAS doesn't follow its own documentation,
sigh.

> What I'd like to see is that the (qp) applies to all instructions generated by the macro

That sounds like an odd definition to me.  I'd expect macros to just be
a text to text translation, not something that has special side effects
such as treating the (qp) differently than normal.  I can see how this
would be useful, but I can also see how this might confuse end users. 
This would have to be well documented as an exception to normal macro
processing.

Another matter to consider here is the -am option, which includes macro
expansions in the listing file.  If we are treating (qp) specially with
macros, then we will also have to update this code, otherwise the
listing files will be wrong with -am.  This may require some hackery in
the macro processing code, which is probably not desirable.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com


  reply	other threads:[~2005-02-17  0:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15 16:06 Jan Beulich
2005-02-17  5:03 ` James E Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-14 12:42 Jan Beulich
2005-02-15 14:30 ` James E Wilson
2005-02-15 14:35   ` H. J. Lu

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=1108599702.27293.101.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).