public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/115239] ICE: internal compiler error: Segmentation fault Date: Mon, 27 May 2024 04:40:40 +0000 [thread overview] Message-ID: <bug-115239-4-sub1qOl2hs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115239-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115239 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2024-05-27 Status|UNCONFIRMED |NEW --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- [apinski@xeond2 gcc]$ ./cc1plus t.cc constexpr bool foo(const char*, char*, long int) constexpr bool foo(const char*, char*, unsigned int) constexpr bool foo(char, char, long int) constexpr bool foo(char, char, unsigned int) t.cc: At global scope: t.cc:7:18: internal compiler error: Segmentation fault 7 | static_assert(foo((char *)nullptr, nullptr, 0)); | ~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 0x134bdbf crash_signal /home/apinski/src/upstream-gcc-match/gcc/gcc/toplev.cc:319 0xa49a4e compare_ics /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/call.cc:12124 0xa5736a joust /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/call.cc:12958 0xa58ee8 tourney /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/call.cc:13476 0xa59068 perform_overload_resolution /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/call.cc:5006 0xa5db12 build_new_function_call(tree_node*, vec<tree_node*, va_gc, vl_embed>**, int) /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/call.cc:5098 0xcadf7d finish_call_expr(tree_node*, vec<tree_node*, va_gc, vl_embed>**, bool, bool, int) /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/semantics.cc:3136 0xc0c2bb cp_parser_postfix_expression /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/parser.cc:8191 0xbe74f0 cp_parser_binary_expression /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/parser.cc:10411 0xbe82b4 cp_parser_assignment_expression /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/parser.cc:10755 0xbe93fd cp_parser_constant_expression /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/parser.cc:11045 0xbeb84b cp_parser_static_assert /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/parser.cc:17096 0xc32672 cp_parser_declaration /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/parser.cc:15706 0xc336fa cp_parser_toplevel_declaration /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/parser.cc:15727 0xc336fa cp_parser_translation_unit /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/parser.cc:5297 0xc336fa c_parse_file() /home/apinski/src/upstream-gcc-match/gcc/gcc/cp/parser.cc:51518 0xd81961 c_common_parse_file() /home/apinski/src/upstream-gcc-match/gcc/gcc/c-family/c-opts.cc:1311 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2024-05-27 4:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-27 4:37 [Bug c++/115239] New: " markus at oberhumer dot com 2024-05-27 4:40 ` pinskia at gcc dot gnu.org [this message] 2024-05-27 4:42 ` [Bug c++/115239] [14/15 Regression] ICE: Segmentation fault with ambiguous function call from static_assert in some cases pinskia at gcc dot gnu.org 2024-05-27 4:43 ` pinskia at gcc dot gnu.org 2024-05-27 4:45 ` [Bug c++/115239] [14/15 Regression] ICE: Segmentation fault with ambiguous function call " pinskia at gcc dot gnu.org 2024-05-27 7:22 ` [Bug c++/115239] [14/15 Regression] ICE: Segmentation fault with ambiguous function call in some cases (`const char*` vs `char` with `long` vs `unsigned`) rguenth at gcc dot gnu.org 2024-05-27 8:52 ` [Bug c++/115239] [14/15 Regression] ICE: Segmentation fault with ambiguous function call in some cases (`const char*` vs `char` with `long` vs `unsigned`) since r14-6522 jakub at gcc dot gnu.org 2024-06-13 14:02 ` cvs-commit at gcc dot gnu.org 2024-06-14 14:50 ` [Bug c++/115239] [14 " ppalka at gcc dot gnu.org 2024-06-17 14:26 ` cvs-commit at gcc dot gnu.org 2024-06-17 14:27 ` ppalka at gcc dot gnu.org 2024-06-24 21:51 ` pinskia 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-115239-4-sub1qOl2hs@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).