public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/19477] sparc64 build fails for default v9 targets: sparc64/soft-fp/qp_itoq.c requires v9a+
Date: Wed, 17 Jan 2024 13:32:03 +0000 [thread overview]
Message-ID: <bug-19477-131-rixkYv70YI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19477-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19477
--- Comment #6 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to John Paul Adrian Glaubitz from comment #5)
> (In reply to Adhemerval Zanella from comment #4)
> > Since 9c8addbc1cd414711310c5a47693f5b0f0b9be3a (2.25) when building for
> > sparc64 the build assumes VIS support (v9a).
>
> What does that mean? Support for SPARC V9 was silently dropped?
I don't think it was even supported [1], we have VIS code forever:
$ git grep "fzero" sysdeps/sparc/sparc64/
sysdeps/sparc/sparc64/fpu/multiarch/s_lrint-vis3.S: fzero ZERO
sysdeps/sparc/sparc64/fpu/multiarch/s_lrintf-vis3.S: fzeros ZERO
sysdeps/sparc/sparc64/fpu/multiarch/s_nearbyint-vis3.S: fzero ZERO
sysdeps/sparc/sparc64/fpu/multiarch/s_nearbyintf-vis3.S: fzeros ZERO
sysdeps/sparc/sparc64/fpu/multiarch/s_rint-vis3.S: fzero ZERO
sysdeps/sparc/sparc64/fpu/multiarch/s_rintf-vis3.S: fzeros ZERO
sysdeps/sparc/sparc64/fpu/s_lrint.S: fzero ZERO
sysdeps/sparc/sparc64/fpu/s_lrintf.S: fzeros ZERO
sysdeps/sparc/sparc64/fpu/s_nearbyint.S: fzero ZERO
sysdeps/sparc/sparc64/fpu/s_nearbyintf.S: fzeros ZERO
sysdeps/sparc/sparc64/fpu/s_rint.S: fzero ZERO
sysdeps/sparc/sparc64/fpu/s_rintf.S: fzeros ZERO
sysdeps/sparc/sparc64/memset.S: fzero %f0
sysdeps/sparc/sparc64/memset.S: fzero %f2
sysdeps/sparc/sparc64/sfp-machine.h: __asm__ __volatile__("fzero
%%f62\n\t" \
sysdeps/sparc/sparc64/sfp-machine.h: __asm ("fzero %%f62\n\t"
\
(So all the work I did for the vis3 ifunc support is pretty much useless)
[1] https://sourceware.org/pipermail/libc-alpha/2016-August/073651.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-17 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19477-131@http.sourceware.org/bugzilla/>
2024-01-17 12:43 ` adhemerval.zanella at linaro dot org
2024-01-17 13:22 ` glaubitz at physik dot fu-berlin.de
2024-01-17 13:32 ` adhemerval.zanella at linaro dot org [this message]
2024-01-17 13:36 ` adhemerval.zanella at linaro dot org
2024-01-17 13:40 ` glaubitz at physik dot fu-berlin.de
2024-01-18 4:59 ` sam at gentoo dot org
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=bug-19477-131-rixkYv70YI@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).