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 c++/107128] armhf: floatn-common.h:214:9: error: multiple types in one declaration Date: Mon, 13 Mar 2023 20:16:54 +0000 [thread overview] Message-ID: <bug-107128-4-Lz0qzBPPZw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107128-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:538a0d0f29b12cff05681b6de2e0a3d7b33f3ef0 commit r13-6643-g538a0d0f29b12cff05681b6de2e0a3d7b33f3ef0 Author: Jason Merrill <jason@redhat.com> Date: Mon Mar 13 14:06:11 2023 -0400 c++: handle _FloatNN redeclaration like bool [PR107128] It's been inconvenient to compile testcases preprocessed with GCC 12 or earlier because they break on typedef __float128 _Float128; We already had code for handling this with bool and wchar_t, it just needs to be extended to _FloatNN as well. PR c++/107128 gcc/cp/ChangeLog: * parser.cc (cp_parser_set_decl_spec_type): Use redefined_builtin_type for extended_float_type_p. gcc/testsuite/ChangeLog: * g++.dg/warn/pragma-system_header6.h: New test. * g++.dg/warn/pragma-system_header6.C: New test.
prev parent reply other threads:[~2023-03-13 20:16 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-03 8:10 [Bug c++/107128] New: " malat at debian dot org 2022-10-03 8:27 ` [Bug c++/107128] " pinskia at gcc dot gnu.org 2022-10-03 8:36 ` malat at debian dot org 2022-10-03 10:07 ` malat at debian dot org 2022-10-03 10:14 ` jakub at gcc dot gnu.org 2022-10-06 10:00 ` rguenth at gcc dot gnu.org 2022-11-18 1:56 ` mh+gcc at glandium dot org 2022-11-18 3:02 ` mh+gcc at glandium dot org 2022-11-18 3:07 ` pinskia at gcc dot gnu.org 2022-11-18 7:51 ` jakub at gcc dot gnu.org 2023-03-13 20:16 ` cvs-commit at gcc dot gnu.org [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=bug-107128-4-Lz0qzBPPZw@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).