From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 170D73858C2C; Sat, 15 Jan 2022 14:03:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 170D73858C2C From: "fxcoudert at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/104042] New: Four memcpy/memset analyzer failures on darwin Date: Sat, 15 Jan 2022 14:03:01 +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.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fxcoudert at gcc dot gnu.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: Sat, 15 Jan 2022 14:03:02 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104042 Bug ID: 104042 Summary: Four memcpy/memset analyzer failures on darwin Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: fxcoudert at gcc dot gnu.org Target Milestone: --- Created attachment 52202 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D52202&action=3Dedit Preprocessed source Some analyzer testcases fail on darwin (https://gcc.gnu.org/pipermail/gcc-testresults/2022-January/747918.html) du= e to what I believe are false positive. Those four cases fail for the same reason: gcc.dg/analyzer/data-model-1.c gcc.dg/analyzer/pr103526.c gcc.dg/analyzer/taint-size-1.c gcc.dg/analyzer/write-to-string-literal-1.c The failures are related to memcpy and memset, and can be reduced to this: $ cat write-to-string-literal-1.c=20 #include void test_2 (void) { memcpy ("abc", "def", 3); /* { dg-warning "write to string literal" } */ } $ ./bin/gcc -fdiagnostics-plain-output -fanalyzer -Wanalyzer-too-complex -fanalyzer-call-summaries write-to-string-literal-1.c -c No warning is emitted, and the test expects a warning. The preprocessed sou= rce for this reduced testcase is attached. The testcase passes if the memcpy() call is replaced by __builtin_memcpy().=