public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90259] ICE: verify_flow_info failed (error: missing REG_EH_REGION note at the end of bb 4)
Date: Tue, 01 Nov 2022 07:19:20 +0000 [thread overview]
Message-ID: <bug-90259-4-SHbE2wlN2f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90259-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90259
--- Comment #4 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #3)
> Aha! I've just managed to reproduce it even w/ the current gcc 13 snapshot
> by adding -fstack-protector-all to the list of command line arguments:
>
> % powerpc-e300c3-linux-gnu-g++-13 -m32 -O1 -ffloat-store -fgcse
> -fnon-call-exceptions -fno-forward-propagate -fno-omit-frame-pointer -c
> svj3x11t.cc -fstack-protector-all
> svj3x11t.cc: In static member function 'static ar p<ar(j ...), i>::as(const
> int&, j ...) [with ar = void; i = q::r; j = {o}]':
> svj3x11t.cc:30:65: error: missing REG_EH_REGION note at the end of bb 6
> 30 | static ar as(const int &p1, j...) { (*ao<i>::ap(p1))(j()...); }
> | ^
It's weird that I still can't reproduce this with the extra option
-fstack-protector-all, I double checked your provided configuration command,
although the host and build are different, the others are the same as mine.
Could you provide one dump file for -mdebug=target?
next prev parent reply other threads:[~2022-11-01 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-90259-4@http.gcc.gnu.org/bugzilla/>
2022-10-19 4:02 ` asolokha at gmx dot com
2022-10-27 6:30 ` linkw at gcc dot gnu.org
2022-10-27 7:44 ` asolokha at gmx dot com
2022-10-27 14:43 ` pinskia at gcc dot gnu.org
2022-11-01 7:19 ` linkw at gcc dot gnu.org [this message]
2022-11-01 7:56 ` asolokha at gmx dot com
2022-11-01 8:16 ` linkw at gcc dot gnu.org
2022-11-02 9:24 ` linkw at gcc dot gnu.org
2022-11-16 2:26 ` cvs-commit at gcc dot gnu.org
2022-11-17 2:28 ` linkw at gcc dot gnu.org
2023-05-14 22:44 ` 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-90259-4-SHbE2wlN2f@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).