From: Patrick Palka <ppalka@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: Jonathan Wakely <jwakely@redhat.com>,
Jonathan Wakely via Libstdc++ <libstdc++@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
hp@gcc.gnu.org
Subject: Re: [committed 2/2] libstdc++: Use GCC's predefined macro for endianness [PR104080]
Date: Tue, 18 Jan 2022 15:01:38 -0500 (EST) [thread overview]
Message-ID: <72d10922-c557-855c-4d86-3b8fca47b100@idea> (raw)
In-Reply-To: <CAMOnLZbZ6pv8MHBa2PEBwJJJr5=MRBFZas9fxBzpaz_KtsDoNQ@mail.gmail.com>
On Tue, 18 Jan 2022, Patrick Palka wrote:
> On Tue, Jan 18, 2022 at 5:12 AM Jonathan Wakely <jwakely@redhat.com> wrote:
> >
> > Tested x86_64-linux, pushed to trunk.
> >
> >
> > Instead of hardcoded preprocessor conditionals with explicit target
> > checks, just rely on the fact that __BYTE_ORDER__ is always defined by
> > GCC.
>
> Thanks a lot for fixing these! I apparently missed removing this
> batch of #includes from the amalgamation in r12-6647. For
> completeness I suppose we should remove these #includes too. I
> wonder if we can rely on __BYTE_ORDER__ being defined by other
> compilers?
(N.B. not just for completeness but potentially also for correctness,
since floating_from_chars.cc #includes "fast_float/fast_float.h" into an
anonymous namespace, and we probably shouldn't be #including system
headers into an anonymous namespace..)
>
> >
> > libstdc++-v3/ChangeLog:
> >
> > PR libstdc++/104080
> > * src/c++17/fast_float/LOCAL_PATCHES: Update.
> > * src/c++17/fast_float/fast_float.h (FASTFLOAT_IS_BIG_ENDIAN):
> > Define in terms of __BYTE_ORDER__.
> > ---
> > libstdc++-v3/src/c++17/fast_float/LOCAL_PATCHES | 1 +
> > libstdc++-v3/src/c++17/fast_float/fast_float.h | 4 +++-
> > 2 files changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/libstdc++-v3/src/c++17/fast_float/LOCAL_PATCHES b/libstdc++-v3/src/c++17/fast_float/LOCAL_PATCHES
> > index 447c7ed2cdb..5bb42933398 100644
> > --- a/libstdc++-v3/src/c++17/fast_float/LOCAL_PATCHES
> > +++ b/libstdc++-v3/src/c++17/fast_float/LOCAL_PATCHES
> > @@ -1,3 +1,4 @@
> > r12-6647
> > r12-6648
> > r12-6664
> > +r12-6665
> > diff --git a/libstdc++-v3/src/c++17/fast_float/fast_float.h b/libstdc++-v3/src/c++17/fast_float/fast_float.h
> > index ee129309ba3..31fb88b8aba 100644
> > --- a/libstdc++-v3/src/c++17/fast_float/fast_float.h
> > +++ b/libstdc++-v3/src/c++17/fast_float/fast_float.h
> > @@ -128,7 +128,9 @@ from_chars_result from_chars_advanced(const char *first, const char *last,
> > #define FASTFLOAT_VISUAL_STUDIO 1
> > #endif
> >
> > -#ifdef _WIN32
> > +#ifdef __BYTE_ORDER__
> > +#define FASTFLOAT_IS_BIG_ENDIAN (__BYTE_ORDER__ == __ORDER_BIG_ENDIAN__)
> > +#elif defined _WIN32
> > #define FASTFLOAT_IS_BIG_ENDIAN 0
> > #else
> > #if defined(__APPLE__) || defined(__FreeBSD__)
> > --
> > 2.31.1
> >
>
next prev parent reply other threads:[~2022-01-18 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 10:12 [committed 1/2] libstdc++: Fix deduction failure for std::min call [PR104080] Jonathan Wakely
2022-01-18 10:12 ` [committed 2/2] libstdc++: Use GCC's predefined macro for endianness [PR104080] Jonathan Wakely
2022-01-18 19:44 ` Patrick Palka
2022-01-18 20:01 ` Patrick Palka [this message]
2022-01-18 20:51 ` Jonathan Wakely
2022-01-18 20:10 ` Jakub Jelinek
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=72d10922-c557-855c-4d86-3b8fca47b100@idea \
--to=ppalka@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.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).