From: Mike Frysinger <vapier@gentoo.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] bfin: Skip non SEC_ALLOC section for R_BFIN_FUNCDESC
Date: Thu, 14 Jan 2021 01:00:02 -0500 [thread overview]
Message-ID: <20210114060002.GI6938@vapier> (raw)
In-Reply-To: <20210113124155.3240078-1-hjl.tools@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
On 13 Jan 2021 04:41, H.J. Lu via Binutils wrote:
> Linker should never generate dynamic relocations for relocations in
> non-SEC_ALLOC section which has no impact on run-time behavior. Such
> relocations should be resolved to 0.
does elf32-frv.c need the same fix ? kind of looks like it.
otherwise, lgtm, thanks
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-14 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 12:41 H.J. Lu
2021-01-14 6:00 ` Mike Frysinger [this message]
2021-01-14 13:28 ` H.J. Lu
2021-01-14 13:31 ` Nick Clifton
2021-01-14 19:40 ` Update my email address (was: Re: [PATCH] bfin: Skip non SEC_ALLOC section for R_BFIN_FUNCDESC) Alexandre Oliva
2021-01-14 20:27 ` [PATCH] bfin: Skip non SEC_ALLOC section for R_BFIN_FUNCDESC Mike Frysinger
2021-01-14 20:36 ` H.J. Lu
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=20210114060002.GI6938@vapier \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
/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).