From: Ken Raeburn <raeburn@cygnus.com>
To: hjl@lucon.org (H.J. Lu)
Cc: rth@cygnus.com, ian@cygnus.com (Ian Lance Taylor), gas2@cygnus.com
Subject: Re: An alpha/gas bug
Date: Mon, 10 Nov 1997 13:25:00 -0000 [thread overview]
Message-ID: <tx1u3dk4fax.fsf@cygnus.com> (raw)
In-Reply-To: <m0xTY06-0004ecC@ocean.lucon.org>
Just as an aside, it's helpful to include the relocs (objdump -dr)
when including this sort of snippet in a bug report. The instructions
alone aren't very informative without the relocs used, when they're
GP-based. (Any interesting changes in the literal sections would be
good to know too.)
> differently. binutils 2.8.1 generates
>
> ldq v0,0(gp)
> lda v0,32(v0)
>
> and gas-971031 generates
>
> ldq v0,0(gp)
>
I'm in the middle of some gcc work right now, but I may look at this
tomorrow if Ian or Richard don't.
Ken
next prev parent reply other threads:[~1997-11-10 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-06 11:54 H.J. Lu
1997-11-10 13:25 ` Ken Raeburn [this message]
1997-11-10 13:25 ` Richard Henderson
1997-11-10 13:31 ` H.J. Lu
[not found] <19971106121644.39437@dot.cygnus.com>
1998-01-24 16:47 ` 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=tx1u3dk4fax.fsf@cygnus.com \
--to=raeburn@cygnus.com \
--cc=gas2@cygnus.com \
--cc=hjl@lucon.org \
--cc=ian@cygnus.com \
--cc=rth@cygnus.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).