public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
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 07:36:00 -0000	[thread overview]
Message-ID: <20020319153605.3490.qmail@sources.redhat.com> (raw)

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

From: Richard Earnshaw <rearnsha@arm.com>
To: Philip Blundell <pb@nexus.co.uk>
Cc: Richard.Earnshaw@arm.com, 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: Tue, 19 Mar 2002 15:25:46 +0000

 pb@nexus.co.uk said:
 > My point was that there are cases where people want to build a "shared
 > object" (in the sense of "gcc -shared") but don't ever intend to have
 > more than one copy of it resident in memory at once.  In that
 > situation, having relocations in the text section is sometimes
 > acceptable for the sake of saving the time and space that is required
 > for the PLT. 
 
 I think that would be better done by adding some sort of import-list 
 support to the linker.  Then only symbols in the import list would need to 
 go through a PLT, and all others could be resolved internally.  For 
 compatible behaviour of course, no import list would imply that all 
 symbols are potentially imported.
 
 R.
 


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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19  7:36 Richard Earnshaw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-23  8:57 rearnsha
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  6:36 Philip Blundell
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=20020319153605.3490.qmail@sources.redhat.com \
    --to=rearnsha@arm.com \
    --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).