public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/53949] [SH] Add support for mac.w / mac.l instructions
Date: Fri, 30 Jan 2015 19:37:00 -0000 [thread overview]
Message-ID: <bug-53949-4-4PtUZV0VAw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53949-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53949
Oleg Endo <olegendo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-01-30
Ever confirmed|0 |1
--- Comment #12 from Oleg Endo <olegendo at gcc dot gnu.org> ---
This is an example from Renesas public material regarding the SH-DSP. The
example program can utilize either the regular mac.w instruction, or the DSP
ISA (found on SH2-DSP, SH3-DSP, SH4AL-DSP).
typedef short Fixed;
typedef long Lfixed;
typedef long Laccum;
#define __X
#define __Y
void func(__X Fixed x[5],Fixed *out, __Y Fixed y[128][5] )
{
int i;
__Y Fixed *yp=y[0];
__X Fixed *xp=x;
Fixed x0,y0;
Lfixed m0;
Laccum a0;
for(i=0;i<128;i++)
{
a0=0;
x0=*xp++; y0=*yp++;
m0=x0*y0; x0=*xp++; y0=*yp++;
a0+=m0; m0=x0*y0; x0=*xp++; y0=*yp++;
a0+=m0; m0=x0*y0; x0=*xp++; y0=*yp++;
a0+=m0; m0=x0*y0; x0=*xp++; y0=*yp++;
a0+=m0; m0=x0*y0;
a0+=m0;
*out++=a0;
}
}
which should compile to something like:
_func:
mov #-128,r1
mov r5,r3
extu.b r1,r1
.L11:
clrmac
mac.w @r6+,@r4+
dt r1
mac.w @r6+,@r4+
mac.w @r6+,@r4+
mac.w @r6+,@r4+
sts macl,r2
mov.w r2,@r3
bf/s .L11
add #2,r3
rts
nop
next prev parent reply other threads:[~2015-01-30 19:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 9:01 [Bug target/53949] New: " olegendo at gcc dot gnu.org
2012-07-13 10:34 ` [Bug target/53949] " olegendo at gcc dot gnu.org
2012-07-13 11:01 ` chrbr at gcc dot gnu.org
2012-07-13 11:24 ` chrbr at gcc dot gnu.org
2012-07-15 12:11 ` olegendo at gcc dot gnu.org
2012-07-17 19:13 ` olegendo at gcc dot gnu.org
2012-07-17 23:05 ` kkojima at gcc dot gnu.org
2012-07-22 16:47 ` olegendo at gcc dot gnu.org
2012-10-11 20:43 ` olegendo at gcc dot gnu.org
2012-11-07 21:31 ` olegendo at gcc dot gnu.org
2013-05-04 13:39 ` olegendo at gcc dot gnu.org
2013-12-17 12:25 ` olegendo at gcc dot gnu.org
2013-12-17 12:37 ` olegendo at gcc dot gnu.org
2015-01-30 19:37 ` olegendo at gcc dot gnu.org [this message]
2015-02-01 0:37 ` olegendo at gcc dot gnu.org
2015-04-08 20:08 ` olegendo 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-53949-4-4PtUZV0VAw@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).