public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <bug-110112-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110112 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=55253&action=edit test case uniname.c (compressed) In a compilation unit with some large read-only static arrays, "gcc -fanalyzer" takes an excessive amount of time: 66 seconds as opposed to less than 1 second without '-fanalyzer'. How to reproduce: $ time gcc -O2 -c uniname.c real 0m0,819s user 0m0,797s sys 0m0,012s $ time gcc -O2 -fanalyzer -c uniname.c <two warnings> real 1m6,195s user 1m6,101s sys 0m0,088s
next reply other threads:[~2023-06-04 11:24 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-04 11:24 bruno at clisp dot org [this message] 2023-06-04 11:30 ` [Bug analyzer/110112] " bruno at clisp dot org 2023-06-04 13:06 ` tlange at gcc dot gnu.org 2023-06-05 6:49 ` rguenth at gcc dot gnu.org 2023-06-08 23:06 ` dmalcolm at gcc dot gnu.org 2023-06-09 22:05 ` cvs-commit at gcc dot gnu.org 2023-06-10 0:54 ` dmalcolm at gcc dot gnu.org 2024-05-09 17:10 ` cvs-commit at gcc dot gnu.org 2024-05-09 17:54 ` [Bug analyzer/110112] [11/12 " dmalcolm at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-110112-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).