public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juchem at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65328] GCC perf issue when compiling templates - 120x slower than Clang Date: Thu, 05 Mar 2015 19:05:00 -0000 [thread overview] Message-ID: <bug-65328-4-iXvFbYOqaq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65328-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65328 --- Comment #7 from juchem at gmail dot com --- Created attachment 34969 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34969&action=edit FWIW, preprocessed file from clang 3.4 generated with: $ time clang++-3.4 -Wall -std=c++11 -E -I . fatal/type/benchmark/prefix_tree_benchmark.cpp > clang-3.4-preprocessed.cpp real 0m0.224s user 0m0.188s sys 0m0.028s
next prev parent reply other threads:[~2015-03-05 19:05 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-05 18:42 [Bug c++/65328] New: " juchem at gmail dot com 2015-03-05 18:47 ` [Bug c++/65328] " pinskia at gcc dot gnu.org 2015-03-05 18:49 ` [Bug c++/65328] New: " Jan Hubicka 2015-03-05 18:49 ` [Bug c++/65328] " hubicka at ucw dot cz 2015-03-05 18:58 ` juchem at gmail dot com 2015-03-05 18:59 ` juchem at gmail dot com 2015-03-05 19:00 ` juchem at gmail dot com 2015-03-05 19:01 ` juchem at gmail dot com 2015-03-05 19:05 ` juchem at gmail dot com [this message] 2015-03-05 19:38 ` trippels at gcc dot gnu.org 2022-06-09 16:01 ` ppalka at gcc dot gnu.org 2022-06-10 20:10 ` cvs-commit at gcc dot gnu.org 2022-06-11 1:23 ` juchem at gmail dot com 2022-06-28 16:24 ` ppalka 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-65328-4-iXvFbYOqaq@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).