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 7A8E33858409; Mon, 28 Aug 2023 13:13:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7A8E33858409
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1693228380;
	bh=LacBJ27En/CFUuKRB4eE4K52Lt6se+FhfEXkqUS4UOE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=dOtP24UXRA6KRJUTEB8EyMyOv7TRHIviftOb1r5eKNv7lN0xcH7gU4JlNhDpeP5qI
	 tMb1LkIhYmLblNMpkxQKzpTm8aw1ppa8aLl3CTu0sEq2JzV0v70hjK4+OMH+wLr5jk
	 Js+vPjIWLqUEUTGlo2O/lT0Hesd7+IzEygI0EEFI=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111211] No warning for iterator going out of scope
Date: Mon, 28 Aug 2023 13:13:00 +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: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-111211-4-jXBLIqVRsY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111211-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111211-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=3D111211

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Lehua Ding from comment #3)
> (In reply to Richard Biener from comment #2)
> > We diagnose this after unrolling, so the difference is whether we unrol=
l or
> > not.
>=20
> But based on the assembly code it looks like both are unrolled.
>=20
> foo:
>         nop
>         nop
>         nop
>         nop
>         nop
>         nop
>         nop
>         xor     eax, eax
>         ret
> foo2:
>         nop
>         nop
>         nop
>         nop
>         nop
>         nop
>         nop
>         nop
>         xor     eax, eax
>         ret

At different times in the pipeline and the warning happens before the second
unrollinb=