public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95305] Same code takes ~1/4 to 1/7th the time to compile under clang++. Date: Wed, 27 May 2020 22:03:36 +0000 [thread overview] Message-ID: <bug-95305-4-eB9VQeeQyt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95305-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95305 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- Using gcc-10 branch and -std=gnu++17 -ftime-report I get a number of errors due to x86 intrinsics and this time report: Time variable usr sys wall GGC phase setup : 0.02 ( 0%) 0.01 ( 0%) 0.04 ( 0%) 1493 kB ( 0%) phase parsing : 55.90 ( 17%) 6.28 ( 11%) 62.34 ( 16%) 3134206 kB ( 37%) phase lang. deferred : 147.04 ( 44%) 49.59 ( 88%) 196.86 ( 50%) 5176483 kB ( 61%) phase opt and generate : 131.22 ( 39%) 0.18 ( 0%) 131.62 ( 34%) 238463 kB ( 3%) |name lookup : 36.29 ( 11%) 6.32 ( 11%) 42.96 ( 11%) 96935 kB ( 1%) |overload resolution : 87.37 ( 26%) 24.47 ( 44%) 113.41 ( 29%) 4175293 kB ( 49%) garbage collection : 5.30 ( 2%) 0.02 ( 0%) 5.32 ( 1%) 0 kB ( 0%) dump files : 0.06 ( 0%) 0.03 ( 0%) 0.10 ( 0%) 0 kB ( 0%) callgraph construction : 130.86 ( 39%) 0.13 ( 0%) 131.12 ( 34%) 159684 kB ( 2%) ipa inheritance graph : 0.01 ( 0%) 0.00 ( 0%) 0.01 ( 0%) 47 kB ( 0%) preprocessing : 1.17 ( 0%) 0.69 ( 1%) 1.55 ( 0%) 72580 kB ( 1%) parser (global) : 1.65 ( 0%) 0.69 ( 1%) 2.85 ( 1%) 210199 kB ( 2%) parser struct body : 1.04 ( 0%) 0.22 ( 0%) 1.08 ( 0%) 97627 kB ( 1%) parser enumerator list : 0.18 ( 0%) 0.04 ( 0%) 0.23 ( 0%) 77970 kB ( 1%) parser function body : 0.32 ( 0%) 0.12 ( 0%) 0.48 ( 0%) 18259 kB ( 0%) parser inl. func. body : 1.17 ( 0%) 0.18 ( 0%) 1.27 ( 0%) 56413 kB ( 1%) parser inl. meth. body : 1.78 ( 1%) 0.51 ( 1%) 2.38 ( 1%) 146304 kB ( 2%) template instantiation : 162.32 ( 49%) 43.83 ( 78%) 206.04 ( 53%) 7604626 kB ( 89%) constant expression evaluation : 27.83 ( 8%) 9.51 ( 17%) 37.73 ( 10%) 26669 kB ( 0%) tree gimplify : 0.17 ( 0%) 0.02 ( 0%) 0.19 ( 0%) 48688 kB ( 1%) tree eh : 0.03 ( 0%) 0.00 ( 0%) 0.04 ( 0%) 5016 kB ( 0%) tree CFG construction : 0.03 ( 0%) 0.00 ( 0%) 0.09 ( 0%) 20079 kB ( 0%) tree CFG cleanup : 0.04 ( 0%) 0.00 ( 0%) 0.03 ( 0%) 14 kB ( 0%) dominance computation : 0.01 ( 0%) 0.00 ( 0%) 0.02 ( 0%) 0 kB ( 0%) varconst : 0.11 ( 0%) 0.04 ( 0%) 0.17 ( 0%) 38 kB ( 0%) loop init : 0.01 ( 0%) 0.00 ( 0%) 0.02 ( 0%) 4933 kB ( 0%) symout : 0.07 ( 0%) 0.02 ( 0%) 0.10 ( 0%) 0 kB ( 0%) TOTAL : 334.18 56.09 390.89 8550662 kB
prev parent reply other threads:[~2020-05-27 22:03 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-24 13:33 [Bug c++/95305] New: Same code takes ~1/10 " gcc-bugs at hussar dot me.uk 2020-05-24 13:34 ` [Bug c++/95305] " gcc-bugs at hussar dot me.uk 2020-05-24 13:53 ` gcc-bugs at hussar dot me.uk 2020-05-25 7:30 ` [Bug c++/95305] Same code takes ~1/4 to 1/7th the " rguenth at gcc dot gnu.org 2020-05-26 9:47 ` gcc-bugs at hussar dot me.uk 2020-05-26 9:48 ` gcc-bugs at hussar dot me.uk 2020-05-27 21:26 ` redi at gcc dot gnu.org 2020-05-27 22:03 ` redi at gcc dot gnu.org [this message]
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-95305-4-eB9VQeeQyt@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).