public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/27558] New: vsprintf() contains function alias with __asm__ label after first use
Date: Wed, 10 Mar 2021 18:30:03 +0000 [thread overview]
Message-ID: <bug-27558-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27558
Bug ID: 27558
Summary: vsprintf() contains function alias with __asm__ label
after first use
Product: glibc
Version: 2.31
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: glaubitz at physik dot fu-berlin.de
CC: adhemerval.zanella at linaro dot org, carlos at redhat dot com,
ebotcazou at gcc dot gnu.org, jrtc27 at jrtc27 dot com
Target Milestone: ---
When building stage2 with clang on sparc64, the build fails with [1]:
In file included from
/var/lib/buildbot/workers/debian-stadler-sparc64/clang-sparc64-linux-multistage/llvm/compiler-rt/lib/sanitizer_common/sanitizer_stackdepot.cpp:17:
In file included from
/var/lib/buildbot/workers/debian-stadler-sparc64/clang-sparc64-linux-multistage/llvm/compiler-rt/lib/sanitizer_common/sanitizer_stackdepotbase.h:16:
In file included from /usr/include/stdio.h:870:
/usr/include/bits/stdio-ldbl.h:26:20: error: cannot apply asm label to function
after its first use
__LDBL_REDIR_DECL (vfprintf)
~~~~~~~~~~~~~~~~~~~^~~~~~~~~
/usr/include/sys/cdefs.h:467:26: note: expanded from macro '__LDBL_REDIR_DECL'
extern __typeof (name) name __asm (__ASMNAME ("__nldbl_" #name));
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
After some research, it turned out to be a bug in glibc which triggers an error
in clang [2] but not gcc. According to the discussion in [2], the different
behavior of clang compared to gcc is intentional and the pattern in question
should actually not exist anymore in glibc. According to the discussion in [1],
the bug triggers on sparc* only since there is no long double math
(__NO_LONG_DOUBLE_MATH) on this target.
> [1] https://bugs.llvm.org/show_bug.cgi?id=48650
> [2] https://bugs.llvm.org/show_bug.cgi?id=22830
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-10 18:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 18:30 glaubitz at physik dot fu-berlin.de [this message]
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
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@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).