public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66002] New: paq8p benchmark 50% slower than clang on sandybridge
Date: Mon, 04 May 2015 07:20:00 -0000	[thread overview]
Message-ID: <bug-66002-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66002

            Bug ID: 66002
           Summary: paq8p benchmark 50% slower than clang on sandybridge
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: trippels at gcc dot gnu.org
  Target Milestone: ---

Created attachment 35451
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35451&action=edit
testcase

On sandybridge I get:

trippels@gcc75 ~ % g++ -O3 -march=native paq8p.ii -o paq8p
trippels@gcc75 ~ % time ./paq8p -4 file1.in
Creating archive with 1 file(s)...
file1.in 262144 -> 262371      
262144 -> 262400
Extracting 1 file(s) from archive -4
Comparing file1.in 262144 -> identical   
./paq8p -4 file1.in  61.82s user 0.08s system 100% cpu 1:01.90 total

trippels@gcc75 ~ % clang++ -w -O3 -march=native paq8p.ii -o paq8p
trippels@gcc75 ~ % time ./paq8p -4 file1.in
...
./paq8p -4 file1.in  29.60s user 0.12s system 100% cpu 29.715 total

Intel compiler:
./paq8p -4 file1.in  22.00s user 0.09s system 99% cpu 22.092 total


             reply	other threads:[~2015-05-04  7:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04  7:20 trippels at gcc dot gnu.org [this message]
2015-05-04 12:47 ` [Bug tree-optimization/66002] " rguenth at gcc dot gnu.org
2015-05-04 12:55 ` trippels at gcc dot gnu.org
2015-05-04 13:43 ` rguenth at gcc dot gnu.org
2015-05-04 13:57 ` rguenth at gcc dot gnu.org
2015-05-04 14:06 ` rguenth at gcc dot gnu.org
2015-05-04 14:11 ` trippels at gcc dot gnu.org
2015-05-06 11:51 ` rguenth at gcc dot gnu.org
2015-05-06 12:13 ` rguenth at gcc dot gnu.org
2015-05-07  9:53 ` rguenth at gcc dot gnu.org
2015-05-07  9:54 ` 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-66002-4@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).