From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-415527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 23958 invoked by alias); 16 Feb 2013 09:37:44 -0000
Received: (qmail 22902 invoked by uid 48); 16 Feb 2013 09:37:23 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55030] [4.8 Regression]: gcc.c-torture/execute/builtins/memcpy-chk.c execution,  -Os (et al)
Date: Sat, 16 Feb 2013 09:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hp at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.0
X-Bugzilla-Changed-Fields: CC
Message-ID: <bug-55030-4-dPK90lje4u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55030-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55030-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2013-02/txt/msg01692.txt.bz2


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

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ebotcazou at gcc dot
                   |                            |gnu.org

--- Comment #10 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2013-02-16 09:37:22 UTC ---
I'm getting back to this because I think that we should reinstate the original
patch, now that the blockage patch has been installed.

I have run into the same issue as your original issue with a private port on
the 4.7 branch: the clobber causes the restoring of the frame pointer to be
deleted
  http://gcc.gnu.org/ml/gcc-patches/2012-10/msg01172.html
Later reload allocates a stack slot to a pseudo that is set before the setjmp
and used after, but the frame pointer doesn't have a consistent value...

Clearly the frame pointer needs to be restored so the clobber is wrong.  It was
there because the final blockage wasn't blocking enough, but the blockage patch
is supposed to have fixed that.