public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/110307] ICE in move_insn, at haifa-sched.cc:5473 when building Ruby on alpha with -fPIC -O2 (or -fpeephole2 -fschedule-insns2)
Date: Sat, 11 Nov 2023 09:01:24 +0000 [thread overview]
Message-ID: <bug-110307-4-2c1Dyd5NMr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110307-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110307
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |uros at gcc dot gnu.org
--- Comment #15 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
It did not bring enlightenment. It looks like INT_MIN REG_EH_REGION annotating
a call that *does not* perform a non-local goto was a late addition, breaking
the assumption "EH_REGION notes may appear only on insns that may throw
exceptions", and now a few places in the compiler look as if they may forget to
preserve the special INT_MIN REG_EH_REGION note.
Uros, would you mind reading the discussion in this bug? Do you have
suggestions how to proceed here?
prev parent reply other threads:[~2023-11-11 9:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 7:08 [Bug rtl-optimization/110307] New: ICE in move_insn, at haifa-sched.cc:5473 on alpha with -fPIC -fpeephole2 -fschedule-insns2 matoro_gcc_bugzilla at matoro dot tk
2023-06-19 11:13 ` [Bug rtl-optimization/110307] " amonakov at gcc dot gnu.org
2023-06-19 20:28 ` [Bug rtl-optimization/110307] ICE in move_insn, at haifa-sched.cc:5473 when building Ruby on alpha with -fPIC -O2 (or -fpeephole2 -fschedule-insns2) matoro_gcc_bugzilla at matoro dot tk
2023-06-19 22:07 ` amonakov at gcc dot gnu.org
2023-06-19 23:02 ` matoro_gcc_bugzilla at matoro dot tk
2023-06-20 9:03 ` amonakov at gcc dot gnu.org
2023-06-20 16:42 ` amonakov at gcc dot gnu.org
2023-06-20 21:45 ` pinskia at gcc dot gnu.org
2023-06-21 11:08 ` amonakov at gcc dot gnu.org
2023-06-22 14:53 ` matoro_gcc_bugzilla at matoro dot tk
2023-06-22 15:55 ` amonakov at gcc dot gnu.org
2023-06-22 16:17 ` matoro_gcc_bugzilla at matoro dot tk
2023-06-25 16:39 ` matoro_gcc_bugzilla at matoro dot tk
2023-06-25 16:46 ` amonakov at gcc dot gnu.org
2023-11-10 21:37 ` sjames at gcc dot gnu.org
2023-11-11 9:01 ` amonakov at gcc dot gnu.org [this message]
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-110307-4-2c1Dyd5NMr@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).