From: Mike Frysinger <vapier@gentoo.org>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: newlib@sourceware.org
Subject: Re: Finish internalization of HAVE_INITFINI_ARRAY work
Date: Sat, 29 Jan 2022 00:15:48 -0500 [thread overview]
Message-ID: <YfTNhPUpKECKi5ba@vapier> (raw)
In-Reply-To: <6d4c8125-1d85-9bbd-3563-82e93baa1e9c@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
On 28 Jan 2022 21:40, Jeff Law wrote:
> Mike's work in this space didn't fix the references to
> HAVE_INITFINI_ARRAY and HAVE_INIT_FINI in libgloss. As a result
> init/fini support was busted for a few targets. or1k had massive GCC
> testsuite failures due to undefined references. cris failed a few tests
> which depended on global ctors/dtors running properly. I don't use
> newlib for testing aarch64 or arm, but they clearly need the same
> obvious change.
>
> Given the obviousness, I'm going to go ahead and install the attached patch.
ack, thanks!
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-01-29 5:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 4:40 Jeff Law
2022-01-29 5:15 ` Mike Frysinger [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=YfTNhPUpKECKi5ba@vapier \
--to=vapier@gentoo.org \
--cc=jeffreyalaw@gmail.com \
--cc=newlib@sourceware.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: 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).