From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-488794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 40504 invoked by alias); 11 Jun 2015 15:57:08 -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 40418 invoked by uid 48); 11 Jun 2015 15:57:04 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66487] [6 Regression] Firefox segfault with LTO enabled
Date: Thu, 11 Jun 2015 15:57: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: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66487-4-z3wnsupSS5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66487-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66487-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: 2015-06/txt/msg01126.txt.bz2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66487

--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> ---
Actually, I guess checking for this is more of a fit for an uninitialized read
detector such as MemorySanitizer or Valgrind memcheck.