public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikeb01 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58928] Different results from gcc when -mlzcnt is used
Date: Fri, 17 Jan 2014 01:18:00 -0000	[thread overview]
Message-ID: <bug-58928-4-tyUZdhjQsB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58928-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Michael Barker <mikeb01 at gmail dot com> ---
> Hope helps

What hardware platform are you testing on?  I'm running on Ivy Bridge:

Intel(R) Xeon(R) CPU E5620 @2.40GHz

Could you put the assembler that you see on the ticket:

With -mlzcnt:

0000000000400580 <lzcnt>:
  400580:    55                       push   %rbp
  400581:    48 89 e5                 mov    %rsp,%rbp
  400584:    48 89 7d e8              mov    %rdi,-0x18(%rbp)
  400588:    48 8b 45 e8              mov    -0x18(%rbp),%rax
  40058c:    48 89 45 f8              mov    %rax,-0x8(%rbp)
  400590:    f3 48 0f bd 45 f8        lzcnt  -0x8(%rbp),%rax
  400596:    48 98                    cltq   
  400598:    5d                       pop    %rbp
  400599:    c3                       retq   

Without -mlzcnt:

0000000000400580 <lzcnt>:
  400580:    55                       push   %rbp
  400581:    48 89 e5                 mov    %rsp,%rbp
  400584:    48 89 7d e8              mov    %rdi,-0x18(%rbp)
  400588:    48 8b 45 e8              mov    -0x18(%rbp),%rax
  40058c:    48 89 45 f8              mov    %rax,-0x8(%rbp)
  400590:    48 0f bd 45 f8           bsr    -0x8(%rbp),%rax
  400595:    48 83 f0 3f              xor    $0x3f,%rax
  400599:    48 98                    cltq   
  40059b:    5d                       pop    %rbp
  40059c:    c3                       retq


  parent reply	other threads:[~2014-01-17  1:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 20:05 [Bug c/58928] New: " mikeb01 at gmail dot com
2013-12-10  7:06 ` [Bug target/58928] " gnome3fans at gmail dot com
2014-01-17  1:18 ` mikeb01 at gmail dot com [this message]
2014-01-17 10:31 ` jtaylor.debian at googlemail dot com
2014-01-17 11:16 ` jakub at gcc dot gnu.org
2014-01-19  0:44 ` mikeb01 at gmail dot com
2014-01-20 23:48 ` mikeb01 at gmail dot com
2014-01-20 23:48 ` mikeb01 at gmail dot com

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-58928-4-tyUZdhjQsB@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).