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/60101] [4.7/4.8/4.9 Regression] Long compile times when mixed complex floating point datatypes are used in lengthy expressions Date: Tue, 11 Feb 2014 13:15:00 -0000 [thread overview] Message-ID: <bug-60101-4-RjcZiFdgS4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60101-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60101 --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 32103 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32103&action=edit WIP patch And just for completeness, I'm attaching my WIP (about 50% of work done) patch to introduce the hash tables. But, if this new testcase doesn't need it, perhaps there is no point in hacking on that further, unless we hit it on larger testcases.
next prev parent reply other threads:[~2014-02-11 13:15 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-06 19:51 [Bug c/60101] New: " thorstenkurth at me dot com 2014-02-07 12:38 ` [Bug c/60101] [4.7/4.8/4.9 Regression] " rguenth at gcc dot gnu.org 2014-02-10 13:59 ` mpolacek at gcc dot gnu.org 2014-02-10 17:29 ` mpolacek at gcc dot gnu.org 2014-02-10 17:43 ` mpolacek at gcc dot gnu.org 2014-02-10 18:12 ` jakub at gcc dot gnu.org 2014-02-10 20:07 ` mpolacek at gcc dot gnu.org 2014-02-11 13:10 ` manu at gcc dot gnu.org 2014-02-11 13:15 ` jakub at gcc dot gnu.org [this message] 2014-02-11 13:17 ` manu at gcc dot gnu.org 2014-02-12 7:36 ` jakub at gcc dot gnu.org 2014-02-12 7:40 ` [Bug c/60101] [4.7/4.8 " jakub at gcc dot gnu.org 2014-03-06 8:02 ` jakub at gcc dot gnu.org 2014-06-12 13:35 ` [Bug c/60101] [4.7 " rguenth 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-60101-4-RjcZiFdgS4@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).