From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2B07B3858407; Thu, 20 Jan 2022 15:49:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2B07B3858407 From: "amacleod at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103121] [12 Regression] Warnings in cp/optimize.c causing build failure Date: Thu, 20 Jan 2022 15:49:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: build, diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: amacleod at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2022 15:49:17 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103121 --- Comment #25 from Andrew Macleod --- OK, lets reset.=20 I run it now, and ranger is indeed being used, so somewhere along the way t= he conversion was finished I guess. so. looking at the trace, I see: 446 range_of_expr(_2) at stmt grp_name_25 =3D __builtin_alloca (_2); 447 range_of_stmt (_2) at stmt _2 =3D _1 + 1; 448 ROS dependence fill ROS dep fill (_2) at stmt _2 =3D _1 + 1; FALSE : (448) ROS (_2) 449 range_of_expr(_1) at stmt _2 =3D _1 + 1; 450 range_of_stmt (_1) at stmt _1 =3D _20->len; TRUE : (450) range_of_stmt (_1) unsigned int VARYING TRUE : (449) range_of_expr (_1) unsigned int VARYING Registering value_relation (_2 !=3D _1) (bb2) at _2 =3D _1 + 1; TRUE : (447) range_of_stmt (_2) unsigned int VARYING TRUE : (446) range_of_expr (_2) unsigned int VARYING So the call to __builtin_alloca is returning VARYING, as one would expect. The original comment#12 from martin was asking that he was seeing [1,1] ins= tead of VARYING for _4 (which is now _2 in this listing I presume) That query should be returning VARYING now, as expected. I also don't get the warning anymore on trunk. Is there still an issue here?=