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 stdio/27087] PowerPC: Redefinition error with Clang from IEEE redirection headers
Date: Thu, 23 Jun 2022 17:54:54 +0000 [thread overview]
Message-ID: <bug-27087-131-bTsc4YBySW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27087-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27087
Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adhemerval.zanella at linaro dot o
| |rg
--- Comment #2 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
I have some local patches that I need to polish to fix it for all definitions
(there are on my azanella/clang branch [1]). I think we will need to adjust
more function that Tulio's patch.
[1]
https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/azanella/clang
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-23 17:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 7:38 [Bug stdio/27087] New: " qiu.chaofan at outlook dot com
2021-10-08 12:33 ` [Bug stdio/27087] " tuliom at ascii dot art.br
2021-10-08 13:00 ` tuliom at ascii dot art.br
2022-06-23 16:46 ` fweimer at redhat dot com
2022-06-23 16:48 ` fweimer at redhat dot com
2022-06-23 17:54 ` adhemerval.zanella at linaro dot org [this message]
2022-06-23 18:27 ` fweimer at redhat dot com
2022-06-30 22:07 ` tuliom at ascii dot art.br
2022-09-10 9:48 ` glaubitz at physik dot fu-berlin.de
2022-11-17 14:37 ` tuliom at ascii dot art.br
2022-11-29 22:36 ` tuliom at ascii dot art.br
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-27087-131-bTsc4YBySW@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).