public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/23601] New: reload may drop non-call exception information Date: Sun, 28 Aug 2005 11:02:00 -0000 [thread overview] Message-ID: <20050828103401.23601.rth@gcc.gnu.org> (raw) Seen as an ia64 bootstrap failure as of 20050828 in libjava/java/lang/reflect/natMethod.cc, though the problem could affect any target. The observed problem is that reload chooses a reg/reg alternative for reloading a memory (for unknown reasons). This causes the insn stream to be changed from (set (reg 1) (mem)) // REG_EH_REGION 1 to (set (reg 2) (addr)) (set (reg 1) (mem)) (set (reg 1) (reg 1)) // REG_EH_REGION 1 so that the insn that actually traps no longer contains the REG_EH_REGION note. I figure the note ought to get distributed during emit_reload_insns. -- Summary: reload may drop non-call exception information Product: gcc Version: 4.1.0 Status: UNCONFIRMED Keywords: wrong-code, ice-on-valid-code Severity: normal Priority: P2 Component: rtl-optimization AssignedTo: rth at gcc dot gnu dot org ReportedBy: rth at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23601
next reply other threads:[~2005-08-28 10:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-28 11:02 rth at gcc dot gnu dot org [this message] 2005-08-28 11:44 ` [Bug rtl-optimization/23601] " pinskia at gcc dot gnu dot org 2005-08-30 6:01 ` phython at gcc dot gnu dot org 2005-08-30 6:05 ` [Bug rtl-optimization/23601] [4.1 Regression] " phython at gcc dot gnu dot org 2005-08-31 16:30 ` cvs-commit at gcc dot gnu dot org 2005-08-31 16:58 ` rth at gcc dot gnu dot 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=20050828103401.23601.rth@gcc.gnu.org \ --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: linkBe 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).