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 11E503858D39; Sun,  4 Jun 2023 11:24:35 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 11E503858D39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1685877875;
	bh=HLgJZJ6l6iNqnrQMV/c6h6FHp8QciCls/qqLtit41YE=;
	h=From:To:Subject:Date:From;
	b=xHqNmkyu98Ly7ILLnfuSZw5MJ785Azk5Zlo8wEg2EhDCMaLdfo0vPsfJJim267fsS
	 ISpii/S6ZxCpY5Cx6XqyxLk9ZGwwQiZCNJS3cThPdtWl8yMt+K1YZWMxmw0gCO/sea
	 eX4yiev7cSOWagvFrU8D7gaNGFswwDq+UrZwTbns=
From: "bruno at clisp dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/110112] New: [11/12/13 Regression] gcc -fanalyzer
 takes an excessive amount of time
Date: Sun, 04 Jun 2023 11:24:34 +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: 13.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bruno at clisp 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: <bug-110112-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=3D110112

            Bug ID: 110112
           Summary: [11/12/13 Regression] gcc -fanalyzer takes an
                    excessive amount of time
           Product: gcc
           Version: 13.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: bruno at clisp dot org
  Target Milestone: ---

Created attachment 55253
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D55253&action=3Dedit
test case uniname.c (compressed)

In a compilation unit with some large read-only static arrays, "gcc -fanaly=
zer"
takes an excessive amount of time: 66 seconds as opposed to less than 1 sec=
ond
without '-fanalyzer'.

How to reproduce:
$ time gcc -O2 -c uniname.c=20

real    0m0,819s
user    0m0,797s
sys     0m0,012s

$ time gcc -O2 -fanalyzer -c uniname.c=20
<two warnings>

real    1m6,195s
user    1m6,101s
sys     0m0,088s=