From: Jeff Law <jeffreyalaw@gmail.com>
To: "Joakim Nohlgård" <joakim@nohlgard.se>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2] gcc: Use ld -r when checking for HAVE_LD_RO_RW_SECTION_MIXING
Date: Sun, 30 Apr 2023 10:35:12 -0600 [thread overview]
Message-ID: <6ea6d799-1c30-db9f-45d9-3164893f2d30@gmail.com> (raw)
In-Reply-To: <20221205134349.1730053-1-joakim@nohlgard.se>
On 12/5/22 06:43, Joakim Nohlgård wrote:
> Fall back to ld -r if ld -shared fails during configure. The check for
> HAVE_LD_RO_RW_SECTION_MIXING can fail on targets where ld does not
> support shared objects, even though the answer to the test should be
> 'read-write'. One such target is riscv64-unknown-elf. Failing this test
> results in a libgcc crtbegin.o which has a writable .eh_frame section
> leading to the default linker scripts placing the .eh_frame section in a
> writable memory segment, or a linker warning when using ld scripts that
> place .eh_frame unconditionally in ROM.
>
> gcc/ChangeLog:
>
> * configure: Regenerate.
> * configure.ac: Use ld -r in the check for HAVE_LD_RO_RW_SECTION_MIXING
Thanks. I've pushed this to the trunk.
jeff
prev parent reply other threads:[~2023-04-30 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 13:43 Joakim Nohlgård
2023-04-30 16:35 ` Jeff Law [this message]
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=6ea6d799-1c30-db9f-45d9-3164893f2d30@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joakim@nohlgard.se \
/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).