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 middle-end/111632] gcc fails to bootstrap when using libc++ Date: Wed, 03 Apr 2024 14:48:10 +0000 [thread overview] Message-ID: <bug-111632-4-is58V2Ty39@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111632-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 --- Comment #24 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>: https://gcc.gnu.org/g:68057560ff1fc0fb2df38c2f9627a20c9a8da5c5 commit r13-8571-g68057560ff1fc0fb2df38c2f9627a20c9a8da5c5 Author: Francois-Xavier Coudert <fxcoudert@gcc.gnu.org> Date: Thu Mar 7 14:36:03 2024 +0100 Include safe-ctype.h after C++ standard headers, to avoid over-poisoning When building gcc's C++ sources against recent libc++, the poisoning of the ctype macros due to including safe-ctype.h before including C++ standard headers such as <list>, <map>, etc, causes many compilation errors, similar to: In file included from /home/dim/src/gcc/master/gcc/gensupport.cc:23: In file included from /home/dim/src/gcc/master/gcc/system.h:233: In file included from /usr/include/c++/v1/vector:321: In file included from /usr/include/c++/v1/__format/formatter_bool.h:20: In file included from /usr/include/c++/v1/__format/formatter_integral.h:32: In file included from /usr/include/c++/v1/locale:202: /usr/include/c++/v1/__locale:546:5: error: '__abi_tag__' attribute only applies to structs, variables, functions, and namespaces 546 | _LIBCPP_INLINE_VISIBILITY | ^ /usr/include/c++/v1/__config:813:37: note: expanded from macro '_LIBCPP_INLINE_VISIBILITY' 813 | # define _LIBCPP_INLINE_VISIBILITY _LIBCPP_HIDE_FROM_ABI | ^ /usr/include/c++/v1/__config:792:26: note: expanded from macro '_LIBCPP_HIDE_FROM_ABI' 792 | __attribute__((__abi_tag__(_LIBCPP_TOSTRING( _LIBCPP_VERSIONED_IDENTIFIER)))) | ^ In file included from /home/dim/src/gcc/master/gcc/gensupport.cc:23: In file included from /home/dim/src/gcc/master/gcc/system.h:233: In file included from /usr/include/c++/v1/vector:321: In file included from /usr/include/c++/v1/__format/formatter_bool.h:20: In file included from /usr/include/c++/v1/__format/formatter_integral.h:32: In file included from /usr/include/c++/v1/locale:202: /usr/include/c++/v1/__locale:547:37: error: expected ';' at end of declaration list 547 | char_type toupper(char_type __c) const | ^ /usr/include/c++/v1/__locale:553:48: error: too many arguments provided to function-like macro invocation 553 | const char_type* toupper(char_type* __low, const char_type* __high) const | ^ /home/dim/src/gcc/master/gcc/../include/safe-ctype.h:146:9: note: macro 'toupper' defined here 146 | #define toupper(c) do_not_use_toupper_with_safe_ctype | ^ This is because libc++ uses different transitive includes than libstdc++, and some of those transitive includes pull in various ctype declarations (typically via <locale>). There was already a special case for including <string> before safe-ctype.h, so move the rest of the C++ standard header includes to the same location, to fix the problem. PR middle-end/111632 gcc/ChangeLog: * system.h: Include safe-ctype.h after C++ standard headers. Signed-off-by: Dimitry Andric <dimitry@andric.com> (cherry picked from commit 9970b576b7e4ae337af1268395ff221348c4b34a)
next prev parent reply other threads:[~2024-04-03 14:48 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-28 16:26 [Bug other/111632] New: gcc's C++ components fail to compile against recent libc++ headers dimitry at andric dot com 2023-09-28 16:26 ` [Bug other/111632] " dimitry at andric dot com 2023-09-29 8:37 ` [Bug middle-end/111632] " rguenth at gcc dot gnu.org 2023-09-29 8:49 ` dimitry at andric dot com 2023-10-05 23:44 ` [Bug middle-end/111632] gcc fails to bootstrap when using libc++ pinskia at gcc dot gnu.org 2023-10-26 16:46 ` dimitry at andric dot com 2023-10-26 16:52 ` sjames at gcc dot gnu.org 2024-02-08 10:56 ` arsen at gcc dot gnu.org 2024-02-08 11:00 ` jakub at gcc dot gnu.org 2024-02-08 12:34 ` arsen at gcc dot gnu.org 2024-02-29 15:10 ` dimitry at andric dot com 2024-03-06 13:38 ` fxcoudert at gcc dot gnu.org 2024-03-06 13:48 ` redi at gcc dot gnu.org 2024-03-06 20:05 ` iains at gcc dot gnu.org 2024-03-06 20:15 ` dimitry@unified-streaming.com 2024-03-06 20:18 ` iains at gcc dot gnu.org 2024-03-06 22:51 ` dimitry at andric dot com 2024-03-06 22:52 ` dimitry at andric dot com 2024-03-07 13:41 ` fxcoudert at gcc dot gnu.org 2024-03-07 18:55 ` dimitry@unified-streaming.com 2024-03-29 19:41 ` iains at gcc dot gnu.org 2024-03-29 20:18 ` dimitry at andric dot com 2024-03-29 23:30 ` gerald at pfeifer dot com 2024-03-30 6:14 ` iains at gcc dot gnu.org 2024-04-03 14:48 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-03 14:49 ` cvs-commit at gcc dot gnu.org 2024-04-03 14:50 ` iains at gcc dot gnu.org 2024-05-09 11:17 ` fxcoudert at gcc dot gnu.org 2024-05-09 11:30 ` ilg at livius dot net 2024-05-09 11:47 ` dimitry at andric dot com 2024-05-09 12:07 ` ilg at livius dot net 2024-05-09 12:12 ` iains at gcc dot gnu.org 2024-05-09 12:12 ` jakub at gcc dot gnu.org 2024-05-09 12:34 ` ilg at livius dot net
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-111632-4-is58V2Ty39@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).