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 62C4D3858426; Wed, 12 Apr 2023 09:07:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 62C4D3858426
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1681290439;
	bh=EKdQPl3fjy6EqKFnmwbbtlSpIyXQyUFEPhF4noMd8Og=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=aE8EqaJj2OezyAFtbVqEEiu/nQx2kd8m1bCiT5o0unB9W/n3MWfDD9SmLyoYRWgUW
	 vmf1WDj9TS5/PxwZ6k6ME35pYOW0PNTLwIiE+b6pLCGDbb453aZ5fHkrreMvkprQkk
	 ll/POp9VsCPgmJder7yfQTRZ2POmFixKeWt1nZkY=
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/109446] Possible destination array overflow without
 diagnosis in memcpy
Date: Wed, 12 Apr 2023 09:07:18 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.4.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
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: 
Message-ID: <bug-109446-4-QokEIkHZpI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109446-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109446-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=3D109446

--- Comment #11 from Martin Li=C5=A1ka <marxin at gcc dot gnu.org> ---
>=20
> Maybe it just happens the end to be on the stack of the inner most functi=
on
> so it just happens that it is an variable address still.

No, that's not the case, see my previous comment.=