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 03:56:00 -0000 [thread overview] Message-ID: <20020319115604.1336.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 <rearnsha@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 11:50:08 +0000 On Tue, 2002-03-19 at 11:09, Richard Earnshaw wrote: > Even if it could be shown that the two relocation types must be > different, then there is no reason for annotating the label in this > way. When assembling PIC code all BL type instructions should generate > a PLT32 relocation (assuming any relocation is required at all) and when > not generating PIC code all BL type instructions should generate an > arm24 relocation. Hence it is possible to determine the relocation type > required simply by the presence of the -k flag on the assembler command > line: no annotation of the labels is required. Yes, quite. 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. I don't see any particularly compelling arguments for either approach over the other, to be honest. It would be easy enough to make gas take notice of -k, and then gcc could do whatever it likes. p.
next reply other threads:[~2002-03-19 11:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-19 3:56 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 6:36 Philip Blundell 2002-03-19 4:06 Richard Earnshaw 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=20020319115604.1336.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: linkBe 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).