public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at geometrian dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107864] New: Internal Compiler Error (Large Project, C++20) Date: Thu, 24 Nov 2022 19:17:57 +0000 [thread overview] Message-ID: <bug-107864-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107864 Bug ID: 107864 Summary: Internal Compiler Error (Large Project, C++20) Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ian at geometrian dot com Target Milestone: --- Created attachment 53962 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53962&action=edit ".zip" file containing "main.cpp", the repro Using g++ built from source yesterday, getting internal compiler error (segfault) on a large C++20 project. A preprocessed file (lightly edited and zipped for file size limit) reproducing the error is attached. Compiled with: g++ main.cpp -std=c++20 -mavx2 The output begins with: In file included from /path/to/mycodedistr/include/mycode/grfx/_cpu/../color/../../_stdafx/matr.hpp:7, from /path/to/mycodedistr/include/mycode/grfx/_cpu/../color/../../_stdafx.hpp:254, from /path/to/mycodedistr/include/mycode/grfx/_cpu/../color/tuples.hpp:3, from /path/to/mycodedistr/include/mycode/grfx/_cpu/framebuffer.hpp:3, from /path/to/mycodedistr/src/mycode/grfx/_cpu/framebuffer.cpp:1: /path/to/mycodedistr/include/mycode/grfx/_cpu/../color/../../_stdafx/_math.hpp: In instantiation of ‘T BR::Math::round(const T&) requires is_floating_point_v<T> [with T = float]’: /path/to/mycodedistr/include/mycode/grfx/color/convert.hpp:132:29: required from here /path/to/mycodedistr/include/mycode/grfx/_cpu/../color/../../_stdafx/_math.hpp:111:23: internal compiler error: Segmentation fault 0x7f3e5c1be51f ??? ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 0x7f3e5c1a5d8f __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 0x7f3e5c1a5e3f __libc_start_main_impl ../csu/libc-start.c:392 Please submit a full bug report "gcc -v" includes: Target: x86_64-pc-linux-gnu Configured with: ../gcc-src/configure --enable-languages=c,c++ --enable-multiarch --program-suffix=-trunk gcc version 13.0.0 20221124 (experimental) (GCC)
next reply other threads:[~2022-11-24 19:17 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-24 19:17 ian at geometrian dot com [this message] 2022-11-24 19:38 ` [Bug c++/107864] " pinskia at gcc dot gnu.org 2022-11-24 21:40 ` pinskia at gcc dot gnu.org 2022-11-24 21:42 ` pinskia at gcc dot gnu.org 2022-11-24 21:48 ` pinskia at gcc dot gnu.org 2022-11-24 21:51 ` [Bug c++/107864] [10/11/12/13 Regression] ICE (seg fault) in check_return_expr with concepts and specialized version pinskia at gcc dot gnu.org 2022-11-24 21:55 ` [Bug c++/107864] [10/11/12/13 Regression] ICE (seg fault) in check_return_expr or instantiate_body " pinskia at gcc dot gnu.org 2022-11-25 0:11 ` redi at gcc dot gnu.org 2022-11-28 16:23 ` ppalka at gcc dot gnu.org 2022-11-29 14:55 ` cvs-commit at gcc dot gnu.org 2022-11-29 15:06 ` [Bug c++/107864] [10/11/12 " ppalka at gcc dot gnu.org 2023-03-07 2:18 ` cvs-commit at gcc dot gnu.org 2023-05-22 3:12 ` [Bug c++/107864] [10/11 " cvs-commit at gcc dot gnu.org 2023-07-07 10:04 ` [Bug c++/107864] [10 " 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-107864-4@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).