public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38587] [4.4 Regression] psim miscompiled #2
Date: Tue, 20 Jan 2009 14:25:00 -0000	[thread overview]
Message-ID: <20090120142458.32560.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38587-296@http.gcc.gnu.org/bugzilla/>



------- Comment #23 from hjl dot tools at gmail dot com  2009-01-20 14:24 -------
(In reply to comment #22)
> From tree-inline.c:
> 
>           case BUILT_IN_LONGJMP:
>             /* We can't inline functions that call __builtin_longjmp at
>                all.  The non-local goto machinery really requires the
>                destination be in a different function.  If we allow the
>                function calling __builtin_longjmp to be inlined into the
>                function calling __builtin_setjmp, Things will Go Awry.  */
> 
> so IMHO we shouldn't inline foo ().  See inline_forbidden_p_stmt.
> 

foo () isn't inlined. We inline bar () which reuses stack slot used
to restore registers after longjmp, which is called from foo ().


-- 


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


  parent reply	other threads:[~2009-01-20 14:25 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-20 15:35 [Bug c/38587] New: psim miscompiled #2 [regression] joel at gcc dot gnu dot org
2008-12-20 18:52 ` [Bug middle-end/38587] " pinskia at gcc dot gnu dot org
2008-12-21  2:17 ` [Bug c/38587] " joel at gcc dot gnu dot org
2009-01-05 14:33 ` [Bug middle-end/38587] " joel at gcc dot gnu dot org
2009-01-05 22:09 ` joel at gcc dot gnu dot org
2009-01-08 22:08 ` joel at gcc dot gnu dot org
2009-01-19 14:07 ` [Bug middle-end/38587] [4.4 Regression] psim miscompiled #2 rguenth at gcc dot gnu dot org
2009-01-19 14:38 ` joel at gcc dot gnu dot org
2009-01-19 14:45 ` joel at gcc dot gnu dot org
2009-01-19 14:51 ` joel at gcc dot gnu dot org
2009-01-19 14:54 ` joel at gcc dot gnu dot org
2009-01-19 15:00 ` joel at gcc dot gnu dot org
2009-01-19 19:01 ` hjl dot tools at gmail dot com
2009-01-19 19:09 ` joel at gcc dot gnu dot org
2009-01-19 19:15 ` joel at gcc dot gnu dot org
2009-01-19 21:38 ` hjl dot tools at gmail dot com
2009-01-19 22:21 ` joel at gcc dot gnu dot org
2009-01-19 23:29 ` hjl dot tools at gmail dot com
2009-01-19 23:35 ` hjl dot tools at gmail dot com
2009-01-19 23:41 ` hjl dot tools at gmail dot com
2009-01-20  2:00 ` hjl dot tools at gmail dot com
2009-01-20  5:00 ` hjl dot tools at gmail dot com
2009-01-20  9:13 ` rguenth at gcc dot gnu dot org
2009-01-20 14:25 ` hjl dot tools at gmail dot com [this message]
2009-01-20 15:02 ` rguenther at suse dot de
2009-01-20 15:08 ` hjl dot tools at gmail dot com
2009-01-20 15:29 ` rguenth at gcc dot gnu dot org
2009-01-20 15:49 ` hjl dot tools at gmail dot com
2009-01-20 15:56 ` joel at gcc dot gnu dot org
2009-01-20 16:30 ` schwab at suse dot de
2009-01-20 16:36 ` hjl dot tools at gmail dot com
2009-01-20 21:17 ` hjl dot tools at gmail dot com
2009-01-20 21:19 ` pinskia at gcc dot gnu dot org
2009-01-21  2:15 ` hjl dot tools at gmail dot com
2009-01-21  3:15 ` vmakarov at redhat dot com
2009-01-21  3:28 ` pinskia at gcc dot gnu dot org
2009-01-21  3:28 ` hjl dot tools at gmail dot com
2009-01-21  3:36 ` pinskia at gcc dot gnu dot org
2009-01-21  9:16 ` schwab at suse dot de
2009-01-21 15:40 ` vmakarov at redhat dot com
2009-01-21 20:04 ` hjl dot tools at gmail dot com
2009-01-21 20:18 ` [Bug middle-end/38587] [4.4 Regression] IRA doesn't preserve local variables after setjmp vmakarov at gcc dot gnu dot org
2009-01-21 21:57 ` rguenth at gcc dot gnu dot org
2009-01-22 19:23 ` joel at gcc dot gnu dot org
2009-01-22 19:34 ` hjl dot tools at gmail dot com

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=20090120142458.32560.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).