public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/36992] Very stange code for _mm_move_epi64 Date: Fri, 01 Aug 2008 12:05:00 -0000 [thread overview] Message-ID: <20080801120430.20697.qmail@sourceware.org> (raw) In-Reply-To: <bug-36992-682@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2008-08-01 12:04 ------- Google leads me to VC++ reference which says "Moves the lower 64 bits of the lower 64 bits of the result, zeroing the upper bits. I guess inlining and type fixing messes this up very early. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36992
next prev parent reply other threads:[~2008-08-01 12:05 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-01 3:30 [Bug target/36992] New: " hjl dot tools at gmail dot com 2008-08-01 11:59 ` [Bug target/36992] " rguenth at gcc dot gnu dot org 2008-08-01 12:05 ` rguenth at gcc dot gnu dot org [this message] 2008-08-01 12:08 ` rguenth at gcc dot gnu dot org 2008-08-01 12:54 ` hjl dot tools at gmail dot com 2008-08-01 12:57 ` hjl dot tools at gmail dot com 2008-08-01 13:22 ` rguenth at gcc dot gnu dot org 2008-08-01 13:27 ` hjl dot tools at gmail dot com 2008-08-01 19:34 ` ubizjak at gmail dot com 2008-08-02 13:10 ` ubizjak at gmail dot com 2008-08-02 13:11 ` ubizjak at gmail dot com 2008-08-02 13:23 ` ubizjak at gmail dot com 2008-08-02 15:08 ` ubizjak at gmail dot com 2008-08-02 15:20 ` hjl dot tools at gmail dot com 2008-08-02 16:03 ` ubizjak at gmail dot com 2008-08-02 18:45 ` ubizjak at gmail dot com 2008-08-03 6:15 ` uros at gcc dot gnu dot org 2008-08-03 6:50 ` ubizjak at gmail dot com 2008-08-05 14:20 ` hjl dot tools at gmail dot com 2008-08-05 17:35 ` hjl dot tools at gmail dot com 2008-08-05 17:42 ` hjl at gcc dot gnu dot org 2008-08-07 13:18 ` hjl at gcc dot gnu dot org 2008-08-07 13:19 ` hjl dot tools 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=20080801120430.20697.qmail@sourceware.org \ --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: linkBe 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).