From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-440929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 20318 invoked by alias); 19 Jan 2014 18:34:40 -0000
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
Received: (qmail 20278 invoked by uid 48); 19 Jan 2014 18:34:36 -0000
From: "eggert at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/48968] incorrect warning about longjmp/vfork clobbering a local (-W -O2, x86-64)
Date: Sun, 19 Jan 2014 18:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eggert at gnu dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-48968-4-eLplx4Jrti@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48968-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-01/txt/msg02071.txt.bz2

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

eggert at gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|FIXED                       |---

--- Comment #9 from eggert at gnu dot org ---
(In reply to Marek Polacek from comment #8)
> Can't reproduce anymore with 4.7/4.8/4.9 (but with 4.6 I can), thus
> hopefully fixed.

Thanks, but which test case did you use, and which version of 4.8?  I can
reproduce the bug with the first test case (u.i) with the GCC 4.8.2 that is
shipped with Fedora 20 (it says it is "gcc (GCC) 4.8.2 20131212 (Red Hat
4.8.2-7)").  That is, the bug with the second test case is fixed with 4.8.2,
but the bug with the first test case remains.