public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113910] [12/13/14 regression] Factor 15 slowdown compiling AMDGPUDisassembler.cpp on SPARC Date: Wed, 14 Feb 2024 09:44:20 +0000 [thread overview] Message-ID: <bug-113910-4-FHfCRhm7Av@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113910-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113910 --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- Note GCC 13 seems to dislike the preprocessed source (odd, 12 and trunk are happy...) In file included from /usr/gcc/11/include/c++/11.4.0/memory:76, from /vol/llvm/src/llvm-project/local/llvm/include/llvm/ADT/SmallVector.h:28, from /vol/llvm/src/llvm-project/local/llvm/include/llvm/ADT/SmallString.h:17, from /vol/llvm/src/llvm-project/local/llvm/lib/Target/AMDGPU/Disassembler/AMDGPUDisassembler.h:19, from /vol/llvm/src/llvm-project/local/llvm/lib/Target/AMDGPU/Disassembler/AMDGPUDisassembler.cpp:19: /usr/gcc/11/include/c++/11.4.0/bits/unique_ptr.h:486:8: error: expected identifier before '__remove_cv' /usr/gcc/11/include/c++/11.4.0/bits/unique_ptr.h:486:20: error: expected '(' before '=' token /usr/gcc/11/include/c++/11.4.0/bits/unique_ptr.h:486:20: error: expected type-specifier before '=' token /usr/gcc/11/include/c++/11.4.0/bits/unique_ptr.h:486:20: error: expected unqualified-id before '=' token /usr/gcc/11/include/c++/11.4.0/bits/unique_ptr.h:492:55: error: wrong number of template arguments (1, should be 2) that's using __remove_cv = typename remove_cv<_Up>::type; template<typename _Up> using __is_derived_Tp = __and_< is_base_of<_Tp, _Up>, __not_<is_same<__remove_cv<_Tp>, __remove_cv<_Up>>> >; I think.
next prev parent reply other threads:[~2024-02-14 9:44 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-13 15:37 [Bug tree-optimization/113910] New: " ro at gcc dot gnu.org 2024-02-13 15:38 ` [Bug tree-optimization/113910] " ro at gcc dot gnu.org 2024-02-13 15:39 ` ro at gcc dot gnu.org 2024-02-13 15:40 ` ro at gcc dot gnu.org 2024-02-13 15:55 ` pinskia at gcc dot gnu.org 2024-02-13 16:04 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-14 9:36 ` rguenth at gcc dot gnu.org 2024-02-14 9:37 ` rguenth at gcc dot gnu.org 2024-02-14 9:44 ` rguenth at gcc dot gnu.org [this message] 2024-02-14 10:05 ` rguenth at gcc dot gnu.org 2024-02-14 10:26 ` rguenth at gcc dot gnu.org 2024-02-14 11:32 ` rguenth at gcc dot gnu.org 2024-02-14 11:41 ` rguenth at gcc dot gnu.org 2024-02-14 14:51 ` rguenth at gcc dot gnu.org 2024-02-14 14:51 ` cvs-commit at gcc dot gnu.org 2024-02-14 15:11 ` [Bug tree-optimization/113910] [12/13 Regression] " rguenth at gcc dot gnu.org 2024-02-14 20:07 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-15 10:43 ` rguenth at gcc dot gnu.org 2024-02-16 12:57 ` rguenth at gcc dot gnu.org 2024-03-21 11:49 ` cvs-commit at gcc dot gnu.org 2024-06-04 8:07 ` [Bug tree-optimization/113910] [12 " cvs-commit at gcc dot gnu.org 2024-06-04 8:09 ` 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-113910-4-FHfCRhm7Av@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).