public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97706] [11 Regression] ICE with LTO at -O3: verify_gimple failed (incompatible types in 'PHI' argument 0)
Date: Wed, 04 Nov 2020 08:51:53 +0000 [thread overview]
Message-ID: <bug-97706-4-N2aYmky5YD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97706-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97706
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |WAITING
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Hmm, please specify how you configured. I do
../src/trunk/configure --target=aarch64-suse-linux
and that doesn't suffice. Any cpu/fpu selection?
As I'm using a cross I do not have libc and thus no runtime objects to link
against and thus trying
> ./xgcc -B. f1.c f2.c -flto -O3 -r -flinker-output=nolto-rel
which works fine. Tried with -march=armv8.2-a+sve as well.
next prev parent reply other threads:[~2020-11-04 8:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 17:46 [Bug tree-optimization/97706] New: " acoplan at gcc dot gnu.org
2020-11-03 17:51 ` [Bug tree-optimization/97706] " acoplan at gcc dot gnu.org
2020-11-04 8:11 ` rguenth at gcc dot gnu.org
2020-11-04 8:51 ` rguenth at gcc dot gnu.org [this message]
2020-11-04 10:42 ` rguenth at gcc dot gnu.org
2020-11-04 13:58 ` marxin at gcc dot gnu.org
2020-11-04 14:31 ` rguenth at gcc dot gnu.org
2020-11-04 14:46 ` rguenth at gcc dot gnu.org
2020-11-04 15:01 ` rguenth at gcc dot gnu.org
2020-11-04 15:07 ` rguenth at gcc dot gnu.org
2020-11-06 11:43 ` cvs-commit at gcc dot gnu.org
2020-11-06 14:00 ` cvs-commit at gcc dot gnu.org
2020-11-06 14:00 ` rguenth 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-97706-4-N2aYmky5YD@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).