public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kaploceh at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 Date: Thu, 20 Oct 2022 07:27:35 +0000 [thread overview] Message-ID: <bug-107327-4-62r8jtRWOe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107327-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327 --- Comment #1 from Carlos E <kaploceh at gmail dot com> --- I haven't had any problems compiling it with Make before, usually it goes into: g++ -O3 -pedantic -std=c++2a -g -Wall -Wextra -Wno-unused-parameter -Wno-sign-compare -Wno-address -Wno-init-list-lifetime -MD -MP -MF <file.d> -c -o <file.o> <file.cc> with the variable CXXFLAGS += -pedantic -std=c++2a -g -Wall -Wextra -Wno-unused-parameter -Wno-sign-compare -Wno-address from the Makefile and so on But this time around, it stops right with the message internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 It finishes by telling me to Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. while GNU Make says Once you have a precise problem you can report it in one of two ways. Either send electronic mail to: bug-make@gnu.org or use our Web-based project management tool, at: http://savannah.gnu.org/projects/make/ So I'm reporting it here rather than over there.
next prev parent reply other threads:[~2022-10-20 7:27 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-20 6:45 [Bug libgcc/107327] New: " kaploceh at gmail dot com 2022-10-20 7:27 ` kaploceh at gmail dot com [this message] 2022-10-20 9:25 ` [Bug c++/107327] " rguenth at gcc dot gnu.org 2022-10-21 7:43 ` kaploceh at gmail dot com 2022-10-21 8:06 ` marxin at gcc dot gnu.org 2022-10-21 8:37 ` kaploceh at gmail dot com 2022-10-21 8:42 ` kaploceh at gmail dot com 2022-10-21 10:40 ` marxin at gcc dot gnu.org 2022-10-23 15:16 ` kaploceh at gmail dot com 2022-10-23 15:19 ` kaploceh at gmail dot com 2022-10-24 8:11 ` marxin at gcc dot gnu.org 2022-11-04 22:20 ` kaploceh at gmail dot com 2022-11-08 14:21 ` marxin 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-107327-4-62r8jtRWOe@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).