From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26946 invoked by alias); 24 Jan 2013 20:50:05 -0000 Received: (qmail 26715 invoked by uid 48); 24 Jan 2013 20:49:36 -0000 From: "manu at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/56094] Invalid line number info generated with tree-level ivopts Date: Thu, 24 Jan 2013 20:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: manu at gcc dot gnu.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-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2013-01/txt/msg02333.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D56094 --- Comment #11 from Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez 2013-01-24 20:49:33 UTC --- (In reply to comment #10) >=20 > Input_location should only be used from parsing. Other places reuse the > variable and those happen to eventually pick up stale values, such as > gimplification. We should > Arrange for different globals to be used there and privatize input_locati= on. In > the meantime assert that input_location is unknown when > Entering or leaving passes. >=20 Perhaps I didn't make myself clear. What is calling internal_get_tmp_var th= at is relying on input_location to be pointing to a sensible location? Is it really called during parsing?