public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104080] [12 Regression] newlib doesn't have endian.h causing build failure with 2800bc08e4ab r12-6646
Date: Tue, 18 Jan 2022 10:04:05 +0000	[thread overview]
Message-ID: <bug-104080-4-65axNSWXV3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104080-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104080

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:8f6b62e0f0c99e421d07bf1847259744db22924b

commit r12-6665-g8f6b62e0f0c99e421d07bf1847259744db22924b
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Jan 18 10:01:23 2022 +0000

    libstdc++: Use GCC's predefined macro for endianness [PR104080]

    Instead of hardcoded preprocessor conditionals with explicit target
    checks, just rely on the fact that __BYTE_ORDER__ is always defined by
    GCC.

    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__.

  parent reply	other threads:[~2022-01-18 10:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  2:10 [Bug libstdc++/104080] New: " hp at gcc dot gnu.org
2022-01-18  2:12 ` [Bug libstdc++/104080] " hp at gcc dot gnu.org
2022-01-18  2:13 ` hp at gcc dot gnu.org
2022-01-18  2:58 ` hp at gcc dot gnu.org
2022-01-18  2:58 ` hp at gcc dot gnu.org
2022-01-18  7:30 ` rguenth at gcc dot gnu.org
2022-01-18  9:27 ` pexu@gcc-bugzilla.mail.kapsi.fi
2022-01-18  9:31 ` redi at gcc dot gnu.org
2022-01-18  9:39 ` redi at gcc dot gnu.org
2022-01-18  9:55 ` cvs-commit at gcc dot gnu.org
2022-01-18 10:04 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-18 10:09 ` redi at gcc dot gnu.org
2022-01-18 11:58 ` hp at gcc dot gnu.org

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-104080-4-65axNSWXV3@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).