public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janezz55 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105064] requires crashes gcc Date: Sun, 27 Mar 2022 18:01:45 +0000 [thread overview] Message-ID: <bug-105064-4-Pj3fcS3R22@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105064-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105064 --- Comment #5 from Janez Zemva <janezz55 at gmail dot com> --- $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /build/gcc/src/gcc/configure --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-bootstrap --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --with-linker-hash-style=gnu --with-system-zlib --enable-__cxa_atexit --enable-cet=auto --enable-checking=release --enable-clocale=gnu --enable-default-pie --enable-default-ssp --enable-gnu-indirect-function --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-multilib --enable-plugin --enable-shared --enable-threads=posix --disable-libssp --disable-libstdcxx-pch --disable-werror --with-build-config=bootstrap-lto --enable-link-serialization=1 gdc_include_dir=/usr/include/dlang/gdc Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.2.0 (GCC) I think the bug has something to do with two classes having the same friend: class A { // friend }; class B { // friend }; c++ is becoming very complex and these crashes are a warning sign. So, you mean I'd have to create an archive and place it here as an attachment? What if it was 1GB in size?
next prev parent reply other threads:[~2022-03-27 18:01 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-26 17:21 [Bug c++/105064] New: " janezz55 at gmail dot com 2022-03-26 20:40 ` [Bug c++/105064] " redi at gcc dot gnu.org 2022-03-27 11:43 ` janezz55 at gmail dot com 2022-03-27 13:00 ` redi at gcc dot gnu.org 2022-03-27 13:02 ` redi at gcc dot gnu.org 2022-03-27 18:01 ` janezz55 at gmail dot com [this message] 2022-03-27 18:05 ` janezz55 at gmail dot com 2022-03-27 18:29 ` janezz55 at gmail dot com 2022-03-27 18:39 ` janezz55 at gmail dot com 2022-03-27 19:16 ` janezz55 at gmail dot com 2022-03-27 22:19 ` [Bug c++/105064] [10/11/12 Regression] " redi at gcc dot gnu.org 2022-03-28 7:30 ` rguenth at gcc dot gnu.org 2022-03-28 13:27 ` ppalka at gcc dot gnu.org 2022-03-28 18:17 ` cvs-commit at gcc dot gnu.org 2022-03-28 18:19 ` [Bug c++/105064] [10/11 " ppalka at gcc dot gnu.org 2022-04-07 19:19 ` cvs-commit at gcc dot gnu.org 2022-05-04 0:24 ` [Bug c++/105064] [10 " ppalka 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-105064-4-Pj3fcS3R22@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).