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:39:41 +0000 [thread overview]
Message-ID: <bug-105064-4-9IteyttJ98@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 #8 from Janez Zemva <janezz55 at gmail dot com> ---
I can reproduce the bug in my rpi4b:
$ g++ -std=c++20 -Ofast loopdemo.cpp -o l
In file included from loopdemo.cpp:3:
loop.hpp:169:55: internal compiler error: Segmentation fault
169 | requires(std::is_same_v<task* const, decltype(tp)>);
| ^
0x7f98a33217 __libc_start_main
../csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-10/README.Bugs> for instructions.
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/10/lto-wrapper
Target: aarch64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 10.2.1-6'
--with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-10
--program-prefix=aarch64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-libquadmath --disable-libquadmath-support --enable-plugin
--enable-default-pie --with-system-zlib --enable-libphobos-checking=release
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch
--enable-fix-cortex-a53-843419 --disable-werror --enable-checking=release
--build=aarch64-linux-gnu --host=aarch64-linux-gnu --target=aarch64-linux-gnu
--with-build-config=bootstrap-lto-lean --enable-link-mutex
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.2.1 20210110 (Debian 10.2.1-6)
next prev parent reply other threads:[~2022-03-27 18:39 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
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 [this message]
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-9IteyttJ98@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: link
Be 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).