public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/96653] Compile time and memory hog w/ -O1 -fanalyzer Date: Tue, 18 Aug 2020 01:21:08 +0000 [thread overview] Message-ID: <bug-96653-4-zuSdIBGvId@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96653-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96653 David Malcolm <dmalcolm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2020-08-18 --- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Thanks for filing this bug; confirmed. Appears to be creating many thousands of constraints; I think it's adding a constraint for every pair of constants for all constants in the switch statements, and thus O(N^2) constraints, where N is the number of constants, or something similar. Gah.
next prev parent reply other threads:[~2020-08-18 1:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-17 11:34 [Bug analyzer/96653] New: " asolokha at gmx dot com 2020-08-18 1:21 ` dmalcolm at gcc dot gnu.org [this message] 2020-09-14 16:29 ` [Bug analyzer/96653] " cvs-commit at gcc dot gnu.org 2020-09-14 16:46 ` [Bug analyzer/96653] -Wanalyzer-too-complex on very large switch statement dmalcolm at gcc dot gnu.org 2020-09-16 23:05 ` cvs-commit at gcc dot gnu.org 2020-09-16 23:30 ` dmalcolm at gcc dot gnu.org 2020-09-16 23:35 ` dmalcolm at gcc dot gnu.org 2020-09-16 23:40 ` 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-96653-4-zuSdIBGvId@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).