public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/47490] __Unwind_SjLj_Unregister clobbers return value with i586-mingw32msvc-g++ 4.4.4 and -fstack-protector
Date: Sun, 30 Jan 2011 02:48:00 -0000	[thread overview]
Message-ID: <bug-47490-4-b3rL6WplUD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47490-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47490

--- Comment #2 from Mikael Pettersson <mikpe at it dot uu.se> 2011-01-30 01:23:33 UTC ---
Fixed on trunk for 4.5 by r146570:

Author: uweigand
Date: Wed Apr 22 11:31:56 2009
New Revision: 146570

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=146570
Log:
    * function.c (expand_function_end): Do not emit a jump to the "naked"
    return label for fall-through returns.
    * except.c (sjlj_emit_function_exit): Always place the call to the
    unregister function at the location installed by expand_function_end.

This seems to have been intended to fix SJLJ miscompilation on SPU, see the
thread starting <http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01265.html>.

Backporting this change to 4.4.5 solves the test case failure there too.


  parent reply	other threads:[~2011-01-30  1:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 14:47 [Bug c++/47490] New: " cyp561 at gmail dot com
2011-01-28 23:58 ` [Bug c++/47490] " mikpe at it dot uu.se
2011-01-30  2:48 ` mikpe at it dot uu.se [this message]
2011-04-12 19:44 ` ktietz at gcc dot gnu.org
2011-04-12 19:45 ` ktietz at gcc dot gnu.org
2011-04-12 19:46 ` ktietz 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-47490-4-b3rL6WplUD@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).