public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: David Palao <david.palao@uv.es>
Cc: gcc-help@gcc.gnu.org
Subject: Re: problems with gcc inline assembly using xmm registers
Date: Fri, 03 Dec 2004 16:37:00 -0000	[thread overview]
Message-ID: <41B09632.8040005@codesourcery.com> (raw)
In-Reply-To: <200412031628.53453.david.palao@uv.es>

David Palao wrote:

> __asm__ __volatile__ ("movsd %0, %%xmm3 \n\t" \
>       "movsd %1, %%xmm6 \n\t" \
>       "movsd %2, %%xmm4 \n\t" \
>       "movsd %3, %%xmm7 \n\t" \
>       "movsd %4, %%xmm5 \n\t" \
>       "unpcklpd %%xmm3, %%xmm3 \n\t" \
>       "unpcklpd %%xmm6, %%xmm6 \n\t" \
>       "unpcklpd %%xmm4, %%xmm4 \n\t" \
>       "mulpd %%xmm0, %%xmm3 \n\t" \
....
>       "addpd %%xmm6, %%xmm5 \n\t" \
>       "addpd %%xmm7, %%xmm3 \n\t" \
>       "movsd %7, %%xmm6 \n\t" \
>       "movsd %8, %%xmm7 \n\t" \
>       "unpcklpd %%xmm6, %%xmm6 \n\t" \
>       "unpcklpd %%xmm7, %%xmm7 \n\t" \
>       "mulpd %%xmm1, %%xmm6 \n\t" \
>       "mulpd %%xmm2, %%xmm7 \n\t" \
>       "addpd %%xmm6, %%xmm4 \n\t" \
>       "addpd %%xmm7, %%xmm5" \

don't write it this way, use the mmx builtins directly and then the
compiler can handle all the register allocation for you.  You'll
have to be careful to arrange for no more than 8 mmx things
to be live at one time though.  That's not too hard to achieve
if you're careful. I had success using this technique to do some
2D FFTs, it was way simpler than writing assembly directly.

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk

  reply	other threads:[~2004-12-03 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 15:29 David Palao
2004-12-03 16:37 ` Nathan Sidwell [this message]
2004-12-03 17:15   ` David Palao
2004-12-03 17:23     ` Nathan Sidwell
     [not found] ` <Pine.LNX.4.61.0412031705390.2211@tripper.tr69.homelinux.net>
2004-12-03 17:42   ` David Palao

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=41B09632.8040005@codesourcery.com \
    --to=nathan@codesourcery.com \
    --cc=david.palao@uv.es \
    --cc=gcc-help@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).