public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: James E Wilson <wilson@tuliptree.org>
To: linux-ia64@vger.kernel.org
Subject: Re: bogus gas error messages
Date: Sat, 22 Jul 2006 03:34:32 +0000	[thread overview]
Message-ID: <1153539271.26845.435.camel@aretha.corp.specifix.com> (raw)
In-Reply-To: <ed5aea430607211009l37cad6afj39cf70865a81d3ef@mail.gmail.com>

On Fri, 2006-07-21 at 10:09, David Mosberger-Tang wrote:
> These are bogus errors in my opinion and should be removed.  For
> example, we already commonly use "saves" to r0 to terminate the
> call-chain.  I'm seeing this with gas v2.17, but it may have been
> around for longer.

This was added by Jan Beulich of Novell on July 1, 2005.  He was fixing
inconsistencies between gas and ias, while trying to port a large body
of code from ias to gas.  So both IAS and the Intel Assembler Language
Guide say that r0/f0/f1 are not valid registers here.  However, the
Intel ALG does not prevent saves to r0.  It is only spillreg and
spillreg.p that aren't allowed to take a readonly register as an
operand.

There is similar language in the Software Conventions and Run-time
Architecure Guide.  In Appendix B, Unwind Descriptor Record Format,
section B.5, in the Format X2 description, it gives encodings for all
registers other than r0/f0/f1.  Looking at this, it is clear that r0 is
a problem here, because the obvious encoding for r0 is actually used by
the restorereg record type.

We can't support spillreg for r0, though we could for f0.  However, we
run the risk that SCRA may someday use the f0 encoding for something
else.  So it seems unwise to do this.

Jim



  reply	other threads:[~2006-07-22  3:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21 17:09 bogus gas error messages David Mosberger-Tang
2006-07-22  3:34 ` James E Wilson [this message]
2006-07-24 16:10 ` David Mosberger-Tang

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=1153539271.26845.435.camel@aretha.corp.specifix.com \
    --to=wilson@tuliptree.org \
    --cc=linux-ia64@vger.kernel.org \
    /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