From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id BE8213858C31; Mon, 10 Jul 2023 06:38:57 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BE8213858C31
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1688971137;
	bh=8SKbJXTGB8u8C4Zlj4q6sNT9YmgO4yQazXlTtk9vC7s=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=PF8MmlSQfkNOnWhmqPwztYvgsYI8y9Rd1Awraex4Eq+fMq3ihNV/U9u+E8JDMajal
	 YOiQTEGxfSG+RdD97HBxqc5vXVbdDppE6HUxlG3BjdUG33VED2f7iODl4NNi2RovB/
	 DfV0sAe2ZINNPcSnEn9H2AJyOrr4XUdQiyFE7mvc=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/110605] Possible lack of error checking in lto-common.cc ?
Date: Mon, 10 Jul 2023 06:38:57 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
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: cf_reconfirmed_on bug_status everconfirmed
Message-ID: <bug-110605-4-Y5GPWNjLTZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110605-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110605-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-07-10
             Status|UNCONFIRMED                 |WAITING
     Ever confirmed|0                           |1

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
If you do -save-temps -v you should see the actual resolution file passed as
-fresolution=3Dfoobar.res to lto1 - can you attach that foobar.res file?=