From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Richard Biener <richard.guenther@gmail.com>,
<gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] longlong.h: Do no use asm input cast for clang
Date: Tue, 10 Jan 2023 20:33:11 +0000 [thread overview]
Message-ID: <1729cf38-40f4-900-e52b-2a2e1467c377@codesourcery.com> (raw)
In-Reply-To: <b067a538-bddb-7c27-ee90-c8f51b43fed9@linaro.org>
On Tue, 10 Jan 2023, Adhemerval Zanella Netto via Gcc-patches wrote:
> That's my original intention [1], but Joseph stated that GCC is the upstream
> source of this file. Joseph, would you be ok for a similar patch to glibc
> since gcc is reluctant to accept it?
I don't think it's a good idea for the copies to diverge. I also think
the file is more heavily used in GCC (as part of the libgcc sources,
effectively) than in glibc and so it's best to use GCC as the upstream for
this shared file.
Ideally maybe most of the macros in this file would be replaced by
built-in functions (that are guaranteed to expand inline rather than
possibly circularly calling a libgcc function defined using the same
macro), so that the inline asm could be avoided (when building libgcc, or
when building glibc with a new-enough compiler). But that would be a
substantial project.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2023-01-10 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 18:16 Adhemerval Zanella
2022-11-30 23:24 ` Segher Boessenkool
2022-12-01 7:26 ` Richard Biener
2022-12-12 18:15 ` Segher Boessenkool
2022-12-12 17:10 ` Adhemerval Zanella Netto
2022-12-12 23:52 ` Segher Boessenkool
2023-01-10 12:26 ` Adhemerval Zanella Netto
2023-01-10 13:20 ` Segher Boessenkool
2023-01-10 14:35 ` Andreas Schwab
2023-01-10 18:20 ` Segher Boessenkool
2023-01-10 20:33 ` Joseph Myers [this message]
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=1729cf38-40f4-900-e52b-2a2e1467c377@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=segher@kernel.crashing.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).