From: Jim Wilson <jimw@sifive.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Upcoming glibc 2.33 freeze in 2 weeks.
Date: Mon, 28 Dec 2020 13:32:01 -0800 [thread overview]
Message-ID: <CAFyWVaZpDUagXU2W3j1j+Q-g6jGuXXvgZoLm0X7FPQsM8-RA8A@mail.gmail.com> (raw)
In-Reply-To: <03617ab6-e0c9-34c0-827e-b654f7b7b2de@redhat.com>
On Tue, Dec 22, 2020 at 7:55 AM Carlos O'Donell via Libc-alpha <
libc-alpha@sourceware.org> wrote:
> The next public patch review meeting is on January 4th 2021
> and my focus will be on patches that need review for the
> release.
>
riscv64-linux has ~50 make check failures using top of tree binutils and
gcc, of which ~30 are ifunc related. This is because we have upstreamed
the binutils and gcc ifunc support, but the glibc ifunc support isn't in
yet. Vincent Chen posted the v2 riscv ifunc patches about 2 weeks ago. It
would be nice to get those in. With those patches in we have ~20
failures. Otherwise, we might need workarounds to get below 25 failures.
Jim
next prev parent reply other threads:[~2020-12-28 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 15:54 Carlos O'Donell
2020-12-28 21:32 ` Jim Wilson [this message]
2020-12-28 21:46 ` Adhemerval Zanella
2021-01-03 11:36 ` Chung-Lin Tang
2021-01-03 13:12 ` Carlos O'Donell
[not found] <c445ecd9-6eb9-6136-3f26-c327c559cf2e () redhat ! com>
2021-01-03 20:43 ` Romain GEISSLER
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=CAFyWVaZpDUagXU2W3j1j+Q-g6jGuXXvgZoLm0X7FPQsM8-RA8A@mail.gmail.com \
--to=jimw@sifive.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@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).