From: Nick Clifton <nickc@redhat.com>
To: Nelson Chu <nelson.chu@sifive.com>,
Lewis Revill <lewis.revill@embecosm.com>,
Alan Modra <amodra@gmail.com>, Jim Wilson <jimw@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] bfd/RISC-V: Prevent region check failures when relaxation is not final
Date: Tue, 5 Oct 2021 15:36:12 +0100 [thread overview]
Message-ID: <28ccabd0-d332-b43c-9d4c-e5e51597dc8b@redhat.com> (raw)
In-Reply-To: <CAJYME4H1Y+_6=6yqmrnysM9RT2d4xVqs=kn-WTDsQ+bZz9b1bw@mail.gmail.com>
Hi Nelson,
>> To fix this, this patch adds the delay_region_check flag to
>> bfd_link_info,
I dislike changing generic code just to fix a problem with one target.
If there is a method that only involves changing risc-v specific code
then I would prefer that. (This is option 3 in PR 28410, right ?)
Cheers
Nick
next prev parent reply other threads:[~2021-10-05 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 15:35 Lewis Revill
2021-10-02 2:54 ` Nelson Chu
2021-10-05 14:36 ` Nick Clifton [this message]
2021-10-06 4:41 ` Nelson Chu
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=28ccabd0-d332-b43c-9d4c-e5e51597dc8b@redhat.com \
--to=nickc@redhat.com \
--cc=amodra@gmail.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=jimw@sifive.com \
--cc=lewis.revill@embecosm.com \
--cc=nelson.chu@sifive.com \
--cc=palmer@dabbelt.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).