public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Jeremie.Detrey at loria dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51393] New: Wrong parameter type for _mm256_insert_epi64 in avxintrin.h
Date: Sat, 03 Dec 2011 11:19:00 -0000	[thread overview]
Message-ID: <bug-51393-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51393
           Summary: Wrong parameter type for _mm256_insert_epi64 in
                    avxintrin.h
    Classification: Unclassified
           Product: gcc
           Version: 4.6.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: Jeremie.Detrey@loria.fr


Created attachment 25978
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25978
Minimal example.

In avxintrin.h:762, the second parameter (__D) of the function
_mm256_insert_epi64 is declared as int where it should be long long.

This results in an uncorrect behavior (truncation to 32 bits then sign
extension) when the attached minimal program is compiled with options -O3
-mavx. A look at the corresponding assembler code confirms this:

  [...]
  vpxor   %xmm0, %xmm0, %xmm0
  movslq  %ebx, %rax
  vpinsrq $0, %rax, %xmm0, %xmm0
  [...]


             reply	other threads:[~2011-12-03 11:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03 11:19 Jeremie.Detrey at loria dot fr [this message]
2011-12-03 11:21 ` [Bug target/51393] " Jeremie.Detrey at loria dot fr
2011-12-03 16:56 ` jakub at gcc dot gnu.org
2011-12-03 17:26 ` Jeremie.Detrey at loria dot fr
2011-12-04 12:48 ` uros at gcc dot gnu.org
2011-12-04 12:52 ` Jeremie.Detrey at loria dot fr
2011-12-04 13:24 ` uros at gcc dot gnu.org
2011-12-04 13:39 ` uros at gcc dot gnu.org
2011-12-04 13:43 ` ubizjak at gmail dot com
2011-12-08 10:59 ` jakub 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-51393-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).