From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 596AC3858438; Mon, 15 Aug 2022 08:55:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 596AC3858438 From: "nrk at disroot dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/106620] New: Incorrectly thinks execution can continue after a return statement Date: Mon, 15 Aug 2022 08:55:35 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: analyzer X-Bugzilla-Version: 12.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: nrk at disroot dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: 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: Mon, 15 Aug 2022 08:55:36 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106620 Bug ID: 106620 Summary: Incorrectly thinks execution can continue after a return statement Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: nrk at disroot dot org Target Milestone: --- Created attachment 53457 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D53457&action=3Dedit sample code Sample code (also attached) : https://godbolt.org/z/ez556Yd39 It thinks that memchr() is being called with null. But if `hay` was null, t= hen the function returns, so that's not possible. Removing the `|| nlen =3D=3D = 1` silences the warning.=