public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/105009] [12 Regression] Fails to build with --target=xtensa-esp32-elf Date: Tue, 22 Mar 2022 17:05:56 +0000 [thread overview] Message-ID: <bug-105009-4-mP3FMp8Cw7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105009-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105009 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- That message is clearly from clang++, when I try: extern inline __attribute__ ((__gnu_inline__)) int tree_to_poly_int64 (int i) { return i + 1; } int tree_to_poly_int64 (int i) { return i + 2; } clang++ complains: error: redefinition of a 'extern inline' function 'tree_to_poly_int64' is not supported in C++ Those inlines in tree.h are guarded with #if !defined ENABLE_TREE_CHECKING && (GCC_VERSION >= 4003) and #define GCC_VERSION (__GNUC__ * 1000 + __GNUC_MINOR__) If you are using the ill-designed -fgnuc-version= option for clang, don't. While I've added a hack for it for libstdc++ headers, there is no way we are going to do this everywhere in GCC sources itself. __GNUC__ macro doesn't mean support for GNU extensions, it means using the GCC compiler or at least something compatible with it up to the version, which perhaps ICC more/less is, but clang certainly is not.
next prev parent reply other threads:[~2022-03-22 17:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-22 2:12 [Bug middle-end/105009] New: " bero at lindev dot ch 2022-03-22 8:44 ` [Bug middle-end/105009] " rguenth at gcc dot gnu.org 2022-03-22 17:05 ` jakub at gcc dot gnu.org [this message] 2022-03-23 8:12 ` 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-105009-4-mP3FMp8Cw7@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).