public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pledr at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/110789] Internal Compiler Error: Illegal instruction
Date: Mon, 24 Jul 2023 08:59:15 +0000 [thread overview]
Message-ID: <bug-110789-4-kQIu2CDic4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110789-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110789
Peter Lezoch <pledr at gmx dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #55617|0 |1
is obsolete| |
--- Comment #2 from Peter Lezoch <pledr at gmx dot net> ---
Created attachment 55618
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55618&action=edit
gcc -v
bash-5.2# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/12.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure --prefix=/usr LD=ld --enable-languages=c,c++
--enable-default-pie --enable-default-ssp --enable-multilib
--with-multilib-list=m64,m32,mx32 --disable-bootstrap --with-system-zlib
--with-long-double-128
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 12.2.0 (GCC)
bash-5.2#
next prev parent reply other threads:[~2023-07-24 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:47 [Bug c/110789] New: " pledr at gmx dot net
2023-07-24 8:55 ` [Bug c/110789] " pinskia at gcc dot gnu.org
2023-07-24 8:59 ` pledr at gmx dot net [this message]
2023-07-24 9:04 ` arsen at gcc dot gnu.org
2023-07-24 15:07 ` pledr at gmx dot net
2023-07-24 16:29 ` pledr at gmx dot net
2023-07-26 6:44 ` pledr at gmx dot net
2023-07-26 6:49 ` pinskia at gcc dot gnu.org
2023-07-27 1:30 ` xry111 at gcc dot gnu.org
2023-07-27 5:05 ` xry111 at gcc dot gnu.org
2023-07-27 5:09 ` xry111 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-110789-4-kQIu2CDic4@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).