public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dushistov at mail dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/57890] gcc 4.8.1 regression: loops become slower Date: Sun, 14 Jul 2013 19:46:00 -0000 [thread overview] Message-ID: <bug-57890-4-BIdsNCeOyT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57890-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57890 --- Comment #3 from Evgeniy Dushistov <dushistov at mail dot ru> --- By the way, here is a short summary of running result of compilation test_loop on my i7 based notebook (the best results): icc(13.1.3 20130607): 0.228 gcc 4.7 : 0.345 gcc 4.8 : 0.4 clang (3.3) : 0.401 so gcc after 4.8 become as slow as clang
next prev parent reply other threads:[~2013-07-14 19:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-57890-4@http.gcc.gnu.org/bugzilla/> 2013-07-12 17:14 ` [Bug target/57890] " pinskia at gcc dot gnu.org 2013-07-13 16:39 ` [Bug tree-optimization/57890] " dushistov at mail dot ru 2013-07-14 19:46 ` dushistov at mail dot ru [this message] 2013-11-09 22:34 ` [Bug target/57890] " pinskia at gcc dot gnu.org 2013-11-09 23:36 ` pinskia at gcc dot gnu.org 2021-06-08 21:37 ` pinskia 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-57890-4-BIdsNCeOyT@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).