From: YunQiang Su <syq@gcc.gnu.org>
To: nickc@redhat.com
Cc: binutils@sourceware.org, macro@orcam.me.uk, xry111@xry111.site
Subject: Re: [PATCH v5] MIPS: Reject branch absolute relocs for PIC for linking
Date: Wed, 21 Feb 2024 16:48:28 +0800 [thread overview]
Message-ID: <CAKcpw6URabfkuBTzzy0ewrvA=itKh1m69h5ws+hDjUW9Gpxuxw@mail.gmail.com> (raw)
In-Reply-To: <20240207173102.2989195-1-syq@gcc.gnu.org>
YunQiang Su <syq@gcc.gnu.org> 于2024年2月8日周四 01:31写道:
>
> The asm code like:
> b (8)
> will emit absolute relocs like:
> R_MIPS_PC16 *ABS*
>
> If they are included into PIC shared objects or PIE executables,
> the branch target will be like 0x12340000, which will make the
> programs crash.
@Maciej ping.
> ---
> bfd/elfxx-mips.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/bfd/elfxx-mips.c b/bfd/elfxx-mips.c
> index 69dd71419ff..9542250dec4 100644
> --- a/bfd/elfxx-mips.c
> +++ b/bfd/elfxx-mips.c
> @@ -9258,6 +9258,15 @@ _bfd_mips_elf_check_relocs (bfd *abfd, struct bfd_link_info *info,
> (h) ? h->root.root.string : "a local symbol");
> break;
> default:
> + if (branch_reloc_p (r_type) && r_symndx == STN_UNDEF)
> + {
> + howto = MIPS_ELF_RTYPE_TO_HOWTO (abfd, r_type, NEWABI_P (abfd));
> + info->callbacks->einfo
> + /* xgettext:c-format */
> + (_("%X%H: relocation %s against `*ABS*' cannot be used"
> + " when making a PIC/PIE object\n"),
> + abfd, sec, rel->r_offset, howto->name);
> + }
> break;
> }
> }
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-02-21 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 17:31 YunQiang Su
2024-02-21 8:48 ` YunQiang Su [this message]
2024-02-21 12:59 ` Maciej W. Rozycki
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='CAKcpw6URabfkuBTzzy0ewrvA=itKh1m69h5ws+hDjUW9Gpxuxw@mail.gmail.com' \
--to=syq@gcc.gnu.org \
--cc=binutils@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=nickc@redhat.com \
--cc=xry111@xry111.site \
/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).