public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/53192] Incorrect arguments to AVX2's gather intrinsics
Date: Tue, 22 May 2012 12:38:00 -0000	[thread overview]
Message-ID: <bug-53192-4-P1b2DkhzHj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53192-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-05-22 11:52:12 UTC ---
BTW, to avoid that warning, you could use in C:
extern __inline __m128i
__attribute__ ((__gnu_inline__, __always_inline__, __artificial__))
_mm_i32gather_epi64 (
#ifdef __cplusplus
                     long long int const *base,
#else
                     union __attribute__((__transparent_union__)) { long long
int const *__ll; long int const *__l; } base,
#endif
                     __m128i index, const int scale)
and for C++ add another overload (of course, for _LP64 only).


  parent reply	other threads:[~2012-05-22 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02 15:41 [Bug target/53192] New: " kirill.yukhin at intel dot com
2012-05-02 15:57 ` [Bug target/53192] " hjl.tools at gmail dot com
2012-05-22  9:57 ` kirill.yukhin at intel dot com
2012-05-22 10:13 ` kirill.yukhin at intel dot com
2012-05-22 12:33 ` jakub at gcc dot gnu.org
2012-05-22 12:38 ` jakub at gcc dot gnu.org [this message]
2024-03-26 23:00 ` pinskia at gcc dot gnu.org
2024-03-26 23:36 ` pinskia at gcc dot gnu.org
2024-03-27 13:38 ` jakub at gcc dot gnu.org
2024-03-27 13:40 ` 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-53192-4-P1b2DkhzHj@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).