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++/104859] [11 Regression] libg++ fails during bootstrap Date: Thu, 07 Apr 2022 19:36:47 +0000 [thread overview] Message-ID: <bug-104859-4-7jeYqZ2Q3F@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104859-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104859 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:c859c99a85b8743b2c1edc097c6f6406de337f45 commit r11-9798-gc859c99a85b8743b2c1edc097c6f6406de337f45 Author: Patrick Palka <ppalka@redhat.com> Date: Wed Mar 9 18:48:52 2022 -0500 libstdc++: Avoid implicit narrowing from uint128_t [PR104859] We need to be explicit about narrowing conversions from uint128_t since, on targets that lack __int128, this type is defined as an integer-class type that is only _explicitly_ convertible to the builtin integer types. This issue was latent until r12-7563-ge32869a17b788b made the frontend correctly reject explicit conversion functions during (dependent) copy-initialization. PR libstdc++/104859 libstdc++-v3/ChangeLog: * src/c++17/floating_to_chars.cc (__floating_to_chars_hex): Be explicit when narrowing the shifted effective_mantissa, since it may have an integer-class type. (cherry picked from commit 65857caee8ccfac5007a9fd0e5f18cce5e5fe934)
next prev parent reply other threads:[~2022-04-07 19:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-09 19:18 [Bug libgcc/104859] New: [12 regression] liibg++ " seurer at gcc dot gnu.org 2022-03-09 21:31 ` [Bug libgcc/104859] " seurer at gcc dot gnu.org 2022-03-09 21:38 ` [Bug c++/104859] " pinskia at gcc dot gnu.org 2022-03-09 21:42 ` seurer at gcc dot gnu.org 2022-03-09 21:45 ` pinskia at gcc dot gnu.org 2022-03-09 22:09 ` ppalka at gcc dot gnu.org 2022-03-09 22:10 ` jakub at gcc dot gnu.org 2022-03-09 22:12 ` jakub at gcc dot gnu.org 2022-03-09 23:49 ` [Bug libstdc++/104859] " cvs-commit at gcc dot gnu.org 2022-03-10 0:04 ` ppalka at gcc dot gnu.org 2022-03-10 8:41 ` [Bug libstdc++/104859] [11 Regression] libg++ " rguenth at gcc dot gnu.org 2022-04-07 10:13 ` rguenth at gcc dot gnu.org 2022-04-07 15:41 ` redi at gcc dot gnu.org 2022-04-07 19:36 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-07 19:38 ` ppalka 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-104859-4-7jeYqZ2Q3F@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: 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).