This is the mail archive of the
mailing list for the glibc project.
Re: [RESEND] [PATCH] PPC64: First in the series of patches implementing
On Thu, Feb 28, 2019 at 10:19 AM Joseph Myers <email@example.com> wrote:
> On Thu, 28 Feb 2019, David Edelsohn wrote:
> > Please stop creating an artificial chicken-and-egg problem. GCC does
> It's not artificial. It's about verifying that the glibc changes actually
> work as intended - in an area where the x86_64 patches, as originally
> committed, *didn't* work as intended (the sincos ABI problem), for the
> lack of such testing (so demonstrating that more testing is needed for
> future libmvec architectures).
> Right now, we have explicit statements from Tulio that the ABI *cannot* be
> confirmed to be as desired, which makes it particularly clear that
> integrating these patches would be premature.
It depends if the patches create any new, public symbols, i.e., if they are
enabled by default. I'll allow Tulio to state his desires instead of applying
biases to other people's statements.
> > not need to implement the vector functionality before it can be merged
> > into GLIBC. One project needs to go first. An implementation in
> > GLIBC that will be leveraged by a future release of GCC is fine.
> > Because of the long pipeline for GLIBC to propagate into Linux
> > distributions, an early GLIBC implementation is very appropriate.
> The glibc freeze for 2.30 starts on 1 July. GCC 9 probably branches in
> late April. There's plenty of time for GCC changes to support this ABI to
> get in before the next glibc freeze (and plenty of time for discussion of
> the glibc patches, and testing with uncommitted GCC patches, before then).
There are a lot of things that can be done. That doesn't make it a