From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-alpha@sourceware.org, DJ Delorie <dj@redhat.com>,
Jim Wilson <jimw@sifive.com>
Subject: Re: [PATCH] csu: Use ELF constructor instead of _init in libc.so
Date: Tue, 25 Feb 2020 13:34:16 +0100 [thread overview]
Message-ID: <87mu96hmlz.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <mvmr1ykw5ud.fsf@suse.de> (Andreas Schwab's message of "Mon, 24 Feb 2020 13:02:50 +0100")
* Andreas Schwab:
> On Feb 24 2020, Florian Weimer wrote:
>
>> Tested on aarch64-linux-gnu, i386-linux-gnu, powerpc64le-linux-gnu,
>> x86_64-linux-gnu. Also built on i686-gnu,
>> riscv64-linux-gnu-rv64imac-lp64, and s390x-linux-gnu.
>>
>> Would someone with access to RISC-V hardware please test this patch?
>
> I have thrown your patch into a test build
> <https://build.opensuse.org/project/show/home:Andreas_Schwab:glibc:test>.
Would you please help me to interpret the results? Is the ppc64le
failure spurious? I can't see any details on the public view.
Thanks,
Florian
next prev parent reply other threads:[~2020-02-25 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 11:09 [PATCH] csu: Use ELF constructor instead of _init in libc.so Florian Weimer
2020-02-24 11:13 ` Andreas Schwab
2020-02-24 12:02 ` Andreas Schwab
2020-02-25 12:34 ` Florian Weimer [this message]
2020-02-25 12:57 ` Andreas Schwab
2020-02-25 12:58 ` Florian Weimer
2020-02-25 13:18 ` Andreas Schwab
2020-02-25 13:44 ` Florian Weimer
2020-02-25 13:53 ` Andreas Schwab
2020-02-25 22:46 ` Alistair Francis
2020-02-24 22:38 ` Jim Wilson
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mu96hmlz.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=dj@redhat.com \
--cc=jimw@sifive.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).