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++/107636] [13 regression] r13-3761-ga239a63f868e29 breaks build on powerpc64le with __float128 support Date: Sat, 12 Nov 2022 20:57:24 +0000 [thread overview] Message-ID: <bug-107636-4-C10SPQeU0m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107636-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107636 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:ec6c2029714057b4bca344ee59be977d17361092 commit r13-3932-gec6c2029714057b4bca344ee59be977d17361092 Author: Jakub Jelinek <jakub@redhat.com> Date: Sat Nov 12 21:56:47 2022 +0100 libstdc++: Fix up to_chars ppc64le _Float128 overloads [PR107636] As reported, I've misplaced __extension__ keywords in these cases (wanted not to have them on the whole inlines because _Float128 is completely standard now while __float128 is not, but before return it is a syntax error. I've verified on a short testcase that both g++ and clang++ accept __extension__ after return keyword. 2022-11-12 Jakub Jelinek <jakub@redhat.com> PR libstdc++/107636 * include/std/charconv (to_chars): Fix up powerpc64le _Float128 overload __extension__ placement.
next prev parent reply other threads:[~2022-11-12 20:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-11 14:37 [Bug libstdc++/107636] New: " enrico.seiler+gccbugs at outlook dot com 2022-11-11 14:40 ` [Bug libstdc++/107636] " enrico.seiler+gccbugs at outlook dot com 2022-11-11 15:39 ` jakub at gcc dot gnu.org 2022-11-11 18:12 ` pinskia at gcc dot gnu.org 2022-11-12 20:57 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-14 11:07 ` rguenth 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-107636-4-C10SPQeU0m@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).