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 9A46B3858C5E; Mon,  4 Dec 2023 11:24:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9A46B3858C5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1701689065;
	bh=jYchwk/uXwPIziun9oaE265DpyOn+6eFNYmIO4vAfu4=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=NW82+Y55VguBaBpnNgi+NmSZVqED8G+HfyXRl4NKg8MqHc4s/xnXaZ5k46XIe69cH
	 bsGbBLk1RyjanKuBK+M0krr/Lnf3cesnGg2hMRgt6FsvPYF6l/nsp1T8dDZJOTcvbO
	 qkMs75Ar1TZRYyqEuFOzohTgP/egHZgnxeXVC5Yg=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112838] Compiler is unable to show the exact error location
 when calling copy ctor for a non-copyable object
Date: Mon, 04 Dec 2023 11:24:25 +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: 10.5.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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: resolution bug_status
Message-ID: <bug-112838-4-FUB3drG7DT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112838-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112838-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=3D112838

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> Confirmed, I thought I had saw an issue filed that is very smilar to this.

See PR 80858 (and PR 58589) and PR 106176 and PR 90413 and others.

I created PR 109551 for the underlying front-end issue.

*** This bug has been marked as a duplicate of bug 109551 ***=