From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 37D633858C56; Sun, 27 Mar 2022 18:01:45 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 37D633858C56
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 11.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janezz55 at gmail dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-105064-4-Pj3fcS3R22@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-105064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-105064-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Mar 2022 18:01:45 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D105064

--- Comment #5 from Janez Zemva <janezz55 at gmail dot com> ---
$ gcc -v
Using built-in specs.
COLLECT_GCC=3Dgcc
COLLECT_LTO_WRAPPER=3D/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=3Dc,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-boots=
trap
--prefix=3D/usr --libdir=3D/usr/lib --libexecdir=3D/usr/lib --mandir=3D/usr=
/share/man
--infodir=3D/usr/share/info --with-bugurl=3Dhttps://bugs.archlinux.org/
--with-linker-hash-style=3Dgnu --with-system-zlib --enable-__cxa_atexit
--enable-cet=3Dauto --enable-checking=3Drelease --enable-clocale=3Dgnu
--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=3Dposix
--disable-libssp --disable-libstdcxx-pch --disable-werror
--with-build-config=3Dbootstrap-lto --enable-link-serialization=3D1
gdc_include_dir=3D/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?=