public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93353] ICE: in final_scan_insn_1, at final.c:3073 (error: could not split insn)
Date: Sat, 27 Feb 2021 20:48:45 +0000 [thread overview]
Message-ID: <bug-93353-4-gyypYzMfJi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93353-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93353
--- Comment #8 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #5)
> (In reply to Segher Boessenkool from comment #4)
> > I cannot get the reduced testcase to fail. Are any special options needed?
>
> If you've been asking me:
Well you reported this, so probably? :-)
> no, the compiler invocation posted in comment 0 is
> explicit, but maybe you need -m32 -f{,no-}PIC -f{,no-}stack-protector which
> one often does for reproducing my PRs because of the configuration I use.
Maybe that is why I so often cannot reproduce your PRs? Please always state
the
exact compiler configuration / invocation needed.
> I'll certainly test the current snapshot, but I won't be able to do so at
> least one more week.
Jakub in comment 7 seems to have found the problem. I cc:ed Alan, who did
4c69e61f4307, which seems to have fixed it on trunk (there is no PR for that
so far?)
next prev parent reply other threads:[~2021-02-27 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93353-4@http.gcc.gnu.org/bugzilla/>
2021-02-26 9:34 ` andrew.goodbody at linaro dot org
2021-02-26 9:43 ` andrew.goodbody at linaro dot org
2021-02-26 9:46 ` andrew.goodbody at linaro dot org
2021-02-27 0:21 ` segher at gcc dot gnu.org
2021-02-27 5:28 ` asolokha at gmx dot com
2021-02-27 8:54 ` jakub at gcc dot gnu.org
2021-02-27 9:02 ` jakub at gcc dot gnu.org
2021-02-27 20:48 ` segher at gcc dot gnu.org [this message]
2021-02-27 20:56 ` segher at gcc dot gnu.org
2024-03-23 23:17 ` pinskia 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-93353-4-gyypYzMfJi@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).