public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/27558] vsprintf() contains function alias with __asm__ label after first use
Date: Wed, 10 Mar 2021 21:43:38 +0000 [thread overview]
Message-ID: <bug-27558-131-WoDSbwmfjt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27558-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27558
--- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 10 Mar 2021, glaubitz at physik dot fu-berlin.de via Glibc-bugs wrote:
> Sure, but I'm surprised that there was no prior discussion to that as both GCC
> and the Linux kernel support SPARC V7, so the removal is rather unfortunate ...
It was discussed on libc-alpha in November 2019.
In practice, the SPARC V7 support had been broken for a long time before
then (the original patch submission says glibc 2.23 / commit
b02840bacdefde318d2ad2f920e50785b9b25d69). So I think the removal was
similar in spirit to the removal of support for the original i386 (de
facto unsupported from glibc 2.4 onwards / the introduction of NPTL, but
it was some years after that before all the i386 code was removed and i486
files moved into the generic i386 locations), which was also about lack of
sufficient atomic operations support.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-10 21:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 18:30 [Bug build/27558] New: " glaubitz at physik dot fu-berlin.de
2021-03-10 18:32 ` [Bug build/27558] " jrtc27 at jrtc27 dot com
2021-03-10 19:16 ` adhemerval.zanella at linaro dot org
2021-03-10 20:05 ` glaubitz at physik dot fu-berlin.de
2021-03-10 20:14 ` adhemerval.zanella at linaro dot org
2021-03-10 20:17 ` glaubitz at physik dot fu-berlin.de
2021-03-10 20:55 ` adhemerval.zanella at linaro dot org
2021-03-10 21:01 ` glaubitz at physik dot fu-berlin.de
2021-03-10 21:43 ` joseph at codesourcery dot com [this message]
2021-03-10 23:01 ` glaubitz at physik dot fu-berlin.de
2021-03-18 8:48 ` glaubitz at physik dot fu-berlin.de
2021-03-18 11:59 ` adhemerval.zanella at linaro dot org
2021-03-22 11:16 ` glaubitz at physik dot fu-berlin.de
2021-04-21 7:13 ` glaubitz at physik dot fu-berlin.de
2021-04-21 8:00 ` fw at deneb dot enyo.de
2022-07-17 7:56 ` glaubitz at physik dot fu-berlin.de
2023-01-09 10:07 ` glaubitz at physik dot fu-berlin.de
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-27558-131-WoDSbwmfjt@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).