From: Ken Raeburn <raeburn@cygnus.com>
To: hjl@nynexst.com (H.J. Lu)
Cc: gas2@cygnus.com, eric@aib.com (Eric Youngdale)
Subject: Re: ELF/x86 as error message
Date: Fri, 30 Sep 1994 13:01:00 -0000 [thread overview]
Message-ID: <9409302001.AA01130@> (raw)
In-Reply-To: <9409300515.AA21112@titanic.nynexst.com>
From: hjl@nynexst.com (H.J. Lu)
Date: Fri, 30 Sep 94 1:16:15 EDT
# gcc-elf -c loop.s
loop.s: Assembler messages:
loop.s:5: Error: Can not do 1 byte pc-relativerelocation
Any reason for ELF/x86 as to do that?
In gas/config/tc-i386.c, the `reloc' function tests for OBJ_ELF, and
shouldn't. The 8- and 16-bit relocations should always be generated.
In the case of ELF, they should always be eliminated before object
file generation, but that happens at a later stage.
And in the error message generated in that function, "pc-relative"
should have a space after it. :-)
prev parent reply other threads:[~1994-09-30 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-09-29 22:16 H.J. Lu
1994-09-30 7:05 ` Eric Youngdale
1994-09-30 13:01 ` Ken Raeburn [this message]
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=9409302001.AA01130@ \
--to=raeburn@cygnus.com \
--cc=eric@aib.com \
--cc=gas2@cygnus.com \
--cc=hjl@nynexst.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).