public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/18032] [4.0.0] SH: wrong code for EH
Date: Mon, 18 Oct 2004 22:43:00 -0000 [thread overview]
Message-ID: <20041018224351.14290.qmail@sourceware.org> (raw)
In-Reply-To: <20041016082157.18032.kkojima@gcc.gnu.org>
------- Additional Comments From kkojima at gcc dot gnu dot org 2004-10-18 22:43 -------
I'm testing a patch you suggest with the usual bootstrap and
regression test. I'll send it to gcc-patches if it passes.
--- ORIG/gcc/gcc/config/sh/sh.c 2004-10-08 07:46:30.000000000 +0900
+++ LOCAL/gcc/gcc/config/sh/sh.c 2004-10-19 07:20:50.000000000 +0900
@@ -5828,6 +5828,10 @@ sh_expand_epilogue (bool sibcall_p)
if (frame_pointer_needed)
{
+ /* We must avoid scheduling the epilogue with previous basic blocks
+ when exception handling is enabled. See PR/18032. */
+ if (flag_exceptions)
+ emit_insn (gen_blockage ());
output_stack_adjust (frame_size, frame_pointer_rtx, e, &live_regs_mask);
/* We must avoid moving the stack pointer adjustment past code
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18032
next prev parent reply other threads:[~2004-10-18 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 8:22 [Bug target/18032] New: " kkojima at gcc dot gnu dot org
2004-10-16 8:26 ` [Bug target/18032] " kkojima at gcc dot gnu dot org
2004-10-16 13:58 ` pinskia at gcc dot gnu dot org
2004-10-18 15:49 ` amylaar at gcc dot gnu dot org
2004-10-18 22:43 ` kkojima at gcc dot gnu dot org [this message]
2004-10-20 13:57 ` cvs-commit at gcc dot gnu dot org
2004-10-20 17:39 ` pinskia 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=20041018224351.14290.qmail@sourceware.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: 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).