public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/58529] Loop 30% faster with Intel than with GCC
Date: Wed, 25 Sep 2013 17:53:00 -0000	[thread overview]
Message-ID: <bug-58529-4-U2tmZoUD7G@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58529-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58529

--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
I actually see gcc 4 times (not just 30%) slower than icpc here using the same
command lines. The asm produced by gcc contains tons of mov insn.


  parent reply	other threads:[~2013-09-25 17:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25 13:06 [Bug middle-end/58529] New: " burnus at gcc dot gnu.org
2013-09-25 13:07 ` [Bug middle-end/58529] " burnus at gcc dot gnu.org
2013-09-25 13:08 ` burnus at gcc dot gnu.org
2013-09-25 14:04 ` glisse at gcc dot gnu.org
2013-09-25 14:59 ` burnus at gcc dot gnu.org
2013-09-25 17:53 ` glisse at gcc dot gnu.org [this message]
2013-09-25 19:35 ` glisse at gcc dot gnu.org
2013-09-25 20:20 ` hjl.tools at gmail dot com
2013-09-26  6:00 ` burnus at gcc dot gnu.org
2013-09-26  7:26 ` [Bug target/58529] GCC -funroll-loops 150% slower with -march=native on x86-64 burnus at gcc dot gnu.org
2013-09-26  7:36 ` burnus at gcc dot gnu.org
2013-10-11  7:51 ` burnus 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-58529-4-U2tmZoUD7G@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: link
Be 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).