public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana.r at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/49452] [4.7 regression] comp-goto-2.c regresses in testing
Date: Wed, 14 Sep 2011 20:55:00 -0000	[thread overview]
Message-ID: <bug-49452-4-QtpIsgiZRn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49452-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #22 from Ramana Radhakrishnan <ramana.r at gmail dot com> 2011-09-14 20:26:43 UTC ---
On 14 Sep 2011, at 07:48, "ebotcazou at gcc dot gnu.org"
<gcc-bugzilla@gcc.gnu.org> wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49452
> 
> --- Comment #21 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-09-14 06:48:01 UTC ---
>> All callee saved registers should never changed after function call. Here fp
>> has been changed is not because it is after a function call, it is because it
>> is after the target of non local goto. I'm not familiar with the implementation
>> of non local goto, but I guess there is some convention/protocol defines which
>> registers may be changed after the target of a non local goto.
> 
> That's not the problem.  The problem is that the blockage isn't honored.


By ?
> 
> -- 
> Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.


  parent reply	other threads:[~2011-09-14 20:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 11:55 [Bug tree-optimization/49452] New: New testsuite failures with arm-linux-gnueabi comp-goto failing with ramana at gcc dot gnu.org
2011-06-17 12:02 ` [Bug tree-optimization/49452] " ramana at gcc dot gnu.org
2011-06-17 16:52 ` [Bug tree-optimization/49452] comp-goto-2.c regresses in testing ebotcazou at gcc dot gnu.org
2011-06-17 16:56 ` ebotcazou at gcc dot gnu.org
2011-06-18  8:38 ` ramana at gcc dot gnu.org
2011-06-20 14:53 ` ramana at gcc dot gnu.org
2011-06-24 22:01 ` janis at gcc dot gnu.org
2011-06-24 22:20 ` eraman at google dot com
2011-06-24 23:03 ` janis at gcc dot gnu.org
2011-06-24 23:05 ` janis at gcc dot gnu.org
2011-06-24 23:06 ` janis at gcc dot gnu.org
2011-06-24 23:09 ` eraman at google dot com
2011-06-27 18:06 ` janis at gcc dot gnu.org
2011-07-14  8:46 ` [Bug tree-optimization/49452] [4.7 regression] " ebotcazou at gcc dot gnu.org
2011-07-14 17:17 ` eraman at google dot com
2011-07-14 22:11 ` eraman at google dot com
2011-07-15  6:26 ` ebotcazou at gcc dot gnu.org
2011-07-16 21:19 ` ebotcazou at gcc dot gnu.org
2011-07-18 16:33 ` ramana at gcc dot gnu.org
2011-07-18 16:36 ` ramana at gcc dot gnu.org
2011-07-18 17:59 ` ebotcazou at gcc dot gnu.org
2011-09-13  8:45 ` carrot at google dot com
2011-09-14  6:27 ` carrot at google dot com
2011-09-14  7:18 ` ebotcazou at gcc dot gnu.org
2011-09-14 20:55 ` ramana.r at gmail dot com [this message]
2011-09-16  7:23 ` carrot at google dot com
2011-09-16 22:05 ` ebotcazou at gcc dot gnu.org
2011-09-20  2:08 ` [Bug rtl-optimization/49452] " carrot at gcc dot gnu.org
2011-10-10 12:22 ` rguenth 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-49452-4-QtpIsgiZRn@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).