public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Philip Blundell <pb@nexus.co.uk>
To: pb@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/3925: [ARM/Thumb] Assembler chokes on branches with  (PLT)
Date: Tue, 19 Mar 2002 06:36:00 -0000	[thread overview]
Message-ID: <20020319143603.10047.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/3925; it has been noted by GNATS.

From: Philip Blundell <pb@nexus.co.uk>
To: Richard.Earnshaw@arm.com
Cc: gcc-gnats@gcc.gnu.org, pb@gcc.gnu.org, fnf@ninemoons.com, 
	gcc-bugs@gcc.gnu.org, rearnsha@gcc.gnu.org
Subject: Re: target/3925: [ARM/Thumb] Assembler chokes on branches with 
	(PLT)
Date: 19 Mar 2002 14:32:39 +0000

 On Tue, 2002-03-19 at 11:55, Richard Earnshaw wrote:
 > OK, so that clears up that side of the problem.  Now, what about the issue 
 > that PLT32 and ARM24 aren't really different relocs?
 
 Well, that depends on your point of view.
 
 Obviously they are the same in terms of the fundamental bit operations
 that they perform on the instruction.  But the PLT32 reloc has some
 extra semantics stacked on top: if the symbol isn't known to be local,
 it generates a plt entry and redirects the branch through it.
 
 You could more or less dispose of the issue by adding an option to the
 linker to say you wanted to generate a PIC executable.  If that was set,
 you would treat all PC24 relocs like PLT32s are now; if not, you would
 treat them as straight PC24.  I think the situation where someone is
 deliberately mixing PIC and PDC objects in order to get a hybrid output
 file is rare enough that it can be neglected.  On the other hand, people
 are accustomed to controlling this with -fPIC at the compilation stage,
 and changing it to be a linker option might turn out to be a nightmare.
 
 p.
 


             reply	other threads:[~2002-03-19 14:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19  6:36 Philip Blundell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-23  8:57 rearnsha
2002-03-19  7:36 Richard Earnshaw
2002-03-19  7:26 Philip Blundell
2002-03-19  7:16 Richard Earnshaw
2002-03-19  7:06 Philip Blundell
2002-03-19  6:56 Richard Earnshaw
2002-03-19  4:06 Richard Earnshaw
2002-03-19  3:56 Philip Blundell
2002-03-19  3:40 rearnsha
2002-03-19  3:16 Richard Earnshaw

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=20020319143603.10047.qmail@sources.redhat.com \
    --to=pb@nexus.co.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=pb@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).