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 04:06:00 -0000	[thread overview]
Message-ID: <20020319120602.9325.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 <rearnsha@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 11:55:57 +0000

 > There's no reason that -k couldn't cause the assembler to emit all
 > branches as PLT32 relocs rather than PC24.  It just happens that Pat and
 > Scott chose to follow the example of the i386-linux port, where the
 > assembler just ignores -k altogether and the compiler adds "@plt"
 > decorations to call instructions.
 
 OK, so that clears up that side of the problem.  Now, what about the issue 
 that PLT32 and ARM24 aren't really different relocs?
 
 R.
 


             reply	other threads:[~2002-03-19 12:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19  4:06 Richard Earnshaw [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  6:36 Philip Blundell
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=20020319120602.9325.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).