public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100041] ICE in curr_insn_transform, at lra-constraints.c:4022
Date: Mon, 12 Apr 2021 07:40:12 +0000 [thread overview]
Message-ID: <bug-100041-4-xo5l21LocT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100041-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100041
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to mss from comment #5)
> (In reply to Martin Liška from comment #4)
> > ... and what compiler options do you use please? Please paste output of
> > --verbose argument.
>
> 0 ~: gcc --verbose
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-apathy-linux-musl/10.3.0/lto-
> wrapper
> Target: x86_64-apathy-linux-musl
> Configured with: ../configure --prefix=/usr --libexecdir=/usr/libexec
> --mandir=/usr/share/man --infodir=/usr/share/info
> --host=x86_64-apathy-linux-musl --build=x86_64-apathy-linux-musl
> --target=x86_64-apathy-linux-musl --with-pkgversion=apathy
> --enable-checking=release --enable-languages=c,c++,lto
> --enable-cxx-flags='-w -pipe -O2 -mtune=native -march=native'
> --with-linker-hash-style=gnu --with-system-zlib --enable-__cxa_atexit
> --enable-linker-build-id --enable-lto --enable-plugin --enable-shared
> --enable-threads=posix --enable-tls --without-included-gettext --without-isl
> --enable-bootstrap --disable-default-pie --disable-default-ssp
> --disable-fixed-point --disable-libmpx --disable-libmudflap
> --disable-libsanitizer --disable-libstdcxx-pch --disable-multilib
> --disable-nls --disable-rpath --disable-static --disable-symvers
> --disable-werror
> Thread model: posix
> Supported LTO compression algorithms: zlib zstd
> gcc version 10.3.0 (apathy)
I need to see the output of --verbose for the compilation invocation that ends
with the internal compiler error.
next prev parent reply other threads:[~2021-04-12 7:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 3:39 [Bug c++/100041] New: " mss at tutanota dot de
2021-04-12 6:17 ` [Bug target/100041] " pinskia at gcc dot gnu.org
2021-04-12 7:30 ` mss at tutanota dot de
2021-04-12 7:32 ` mss at tutanota dot de
2021-04-12 7:34 ` marxin at gcc dot gnu.org
2021-04-12 7:39 ` mss at tutanota dot de
2021-04-12 7:40 ` marxin at gcc dot gnu.org [this message]
2021-04-12 8:52 ` mss at tutanota dot de
2021-04-12 8:54 ` mss at tutanota dot de
2021-04-12 8:55 ` mss at tutanota dot de
2021-04-12 9:08 ` mss at tutanota dot de
2021-04-12 9:09 ` rguenth at gcc dot gnu.org
2021-04-12 9:11 ` rguenth at gcc dot gnu.org
2021-04-12 9:31 ` ubizjak at gmail dot com
2021-04-12 11:08 ` marxin at gcc dot gnu.org
2021-04-12 11:21 ` ubizjak at gmail dot com
2021-04-12 11:57 ` ubizjak at gmail dot com
2021-04-12 11:59 ` ubizjak at gmail dot com
2021-04-12 12:04 ` jakub at gcc dot gnu.org
2021-04-12 12:11 ` ubizjak at gmail dot com
2021-04-12 12:14 ` jakub at gcc dot gnu.org
2021-04-12 12:22 ` ubizjak at gmail dot com
2021-04-12 12:26 ` mss at tutanota dot de
2021-04-23 16:46 ` cvs-commit at gcc dot gnu.org
2021-04-24 8:03 ` ubizjak at gmail dot com
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-100041-4-xo5l21LocT@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).