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 2386B3858C30; Thu,  1 Jun 2023 00:07:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2386B3858C30
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1685578053;
	bh=PTHotf+X8eTVrKKgJJS/nUX7JrABP4Pd1kxlmu4lh+0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=wUF1mEU/P8pLDGIjvZBZLpFw7ASV5JDj0FaeYgmnjybEoTvPXqXNUUxwEZESHv1L0
	 E6og2n1kQjmhKQHRyMN+95m+p0bot/cdOwozHUtrVcLB6wLaF6dX4WjjfvMR4q3uLz
	 T+u0wVuO6FzO4W7gZck9TMO7d4U79X1bapXLbjiA=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110055] Dangling pointer warning inside std::vector
 on RISC-V
Date: Thu, 01 Jun 2023 00:07:32 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 13.1.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-110055-4-lTy3SMeHtQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110055-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110055-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=3D110055

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> >  C.0 =3D{v} {CLOBBER(eol)};
>=20
>=20
> Should never have been emitted from the gimplifier.
>=20
>=20
> Confirmed, I have not reduced the testcase yet.
> But I can also confirm it on aarch64-linux-gnu with -O3 -mstrict-align
> -fno-exceptions .

So what is happening is we emitting the clobber and then changing it to be a
static variable.

This part happens even for x86_64 though the memcpy here can be removed.


      C.0 =3D {CLOBBER(eol)};=