public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46401] [4.5/4.6 Regression] very slow compile time with -Wsequence-point Date: Mon, 15 Nov 2010 16:27:00 -0000 [thread overview] Message-ID: <bug-46401-4-XrWoNTe7s1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46401-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46401 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org |gnu.org | --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-11-15 16:21:11 UTC --- Created attachment 22401 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22401 gcc46-pr46401.patch Untested fix. No point tracking CALL_EXPRs that aren't ECF_CONST (because then operand_equal_p fails anyway) nor STRING_CSTs (which can't be written into). That said, -Wsequence-point algorithm is still quadratic (certainly in used memory, and at least quadratic in compilation time).
next prev parent reply other threads:[~2010-11-15 16:22 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-09 21:30 [Bug c++/46401] New: " zsojka at seznam dot cz 2010-11-10 12:08 ` [Bug c++/46401] " rguenth at gcc dot gnu.org 2010-11-15 16:27 ` jakub at gcc dot gnu.org [this message] 2010-11-16 21:11 ` jakub at gcc dot gnu.org 2010-11-16 21:31 ` [Bug c++/46401] [4.5 " jakub at gcc dot gnu.org 2010-11-25 16:02 ` rguenth at gcc dot gnu.org 2010-12-07 15:06 ` jakub at gcc dot gnu.org 2010-12-07 15:40 ` jakub 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-46401-4-XrWoNTe7s1@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).