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/27558] vsprintf() contains function alias with __asm__ label after first use Date: Wed, 10 Mar 2021 19:16:42 +0000 [thread overview] Message-ID: <bug-27558-131-JspNQtUr9R@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 #2 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- If I understood correctly the issue is asm alias is declared *after* the function prototype, right? Does the fix from https://bugs.llvm.org/show_bug.cgi?id=48650#c4 fix the issue without any regression? If so I can check if it breaks anything on other architectures and prepare a patch. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-10 19:16 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 [this message] 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-JspNQtUr9R@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: linkBe 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).