public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/48542] mmix code which calls setjmp/longjmp may not work.
Date: Tue, 14 Jun 2011 07:12:00 -0000 [thread overview]
Message-ID: <bug-48542-4-QtRqSvQodk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48542-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48542
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #23938|0 |1
is obsolete| |
--- Comment #6 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2011-06-14 07:12:04 UTC ---
Created attachment 24516
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24516
Fix for trunk and maybe branches
Patch against trunk r174961. Fixes in two places (reload.c:find_equiv_reg and
reload1.c:reload_as_needed) are necessary, because when register contents is
invalidated for the main path (the patch to reload1.c), there's fallback code
that also iterates over code, and which also lacks proper handling of
setjmp-type calls. So, you can see this bug on other targets if you're
"unlucky" enough to write code that need reloads and which seems reusable
across a setjmp-call.
This just naturally happens more often for mmix (like always), given that (set
rJ (mem ...)) is emitted after every call and always needs a reload through a
general register, and is always reloaded from the same mem.
(Tentative partial analysis.)
next prev parent reply other threads:[~2011-06-14 7:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-48542-4@http.gcc.gnu.org/bugzilla/>
2011-06-04 14:33 ` hp at gcc dot gnu.org
2011-06-07 5:46 ` hp at gcc dot gnu.org
2011-06-14 7:03 ` hp at gcc dot gnu.org
2011-06-14 7:12 ` hp at gcc dot gnu.org [this message]
2011-06-17 2:18 ` [Bug rtl-optimization/48542] " hp at gcc dot gnu.org
2011-06-17 2:20 ` hp at gcc dot gnu.org
2011-06-17 2:22 ` hp at gcc dot gnu.org
2011-06-17 11:14 ` hp at gcc dot gnu.org
2011-06-17 11:16 ` hp at gcc dot gnu.org
2011-06-17 11:18 ` hp at gcc dot gnu.org
2011-06-17 11:18 ` hp at gcc dot gnu.org
2011-06-17 11:20 ` hp at gcc dot gnu.org
2011-06-17 11:21 ` hp at gcc dot gnu.org
2011-06-17 11:25 ` hp at gcc dot gnu.org
2011-06-17 11:26 ` hp at gcc dot gnu.org
2011-06-17 11:38 ` [Bug rtl-optimization/48542] unchanged variables in code which calls setjmp may be clobbered (including the return-address) hp at gcc dot gnu.org
2012-06-17 9:19 ` ebotcazou 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-48542-4-QtRqSvQodk@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).