From: Ankit Jain <ankitjain1580@yahoo.com>
To: James HAUXWELL <james.hauxwell@st.com>, gcc-help@gcc.gnu.org
Subject: Re: Can't generate a 'movd' instructuction
Date: Sat, 27 Nov 2004 05:25:00 -0000 [thread overview]
Message-ID: <20041127052541.18384.qmail@web52905.mail.yahoo.com> (raw)
In-Reply-To: <41A6E0B7.60909@st.com>
hi
--- James HAUXWELL <james.hauxwell@st.com> wrote:
> Hi,
>
> I have a piece of code using mmx/sse intrinsics
>
> ta = __builtin_ia32_pmaddwd(ia, one);
> tb = (v2si)__builtin_ia32_psrlq((di)ta, 32);
> dest.__v = __builtin_ia32_paddd(ta, tb);
> satd = dest.__a[0];
>
> At the phase where I move the bottom 32bits of the
> mmx register to a
> normal register
well i have a doubt in this i.e whether this is really
happening or not. because i am also usign gcc compiler
only and movd instrction works. if your things work
let me also know about it
thanks
I should be able to use a movd
> instruction (according to
> intel documentation), but what ever I do I can't
> generate one. It is
> currently generating a movq to a memory loacation
> and then doing a
> shorter load from the same location.
>
> should be something like.
>
> ta = __builtin_ia32_pmaddwd(ia, one);
> tb = (v2si)__builtin_ia32_psrlq((di)ta, 32);
> satd = (int)__builtin_ia32_paddd(ta, tb);
>
> Is anyone familiar enough with intrinsics to know
> why this doesn't work?
>
> Jim
>
________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html
next prev parent reply other threads:[~2004-11-27 5:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 7:52 James HAUXWELL
2004-11-26 8:32 ` Sriharsha Vedurmudi
2004-11-27 5:25 ` Ankit Jain [this message]
2004-11-29 8:22 ` James HAUXWELL
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=20041127052541.18384.qmail@web52905.mail.yahoo.com \
--to=ankitjain1580@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
--cc=james.hauxwell@st.com \
/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).