From: "Kevin D. Kissell" <kevink@mips.com>
To: <Amit.Lubovsky@infineon.com>, <linux-mips@linux-mips.org>
Subject: Re: mips5kc - cpu registers
Date: Mon, 31 Mar 2003 19:21:29 +0200 [thread overview]
Message-ID: <009401c2f7aa$0137f2a0$10eca8c0@grendel> (raw)
In-Reply-To: 04C8EDC5AE3FD611ABE40002B39CF69B07F37F@ntah901e.savan.com
In general, gcc (and most other compilers)
will do this for you automatically if you enable
any reasonable level of optimization. There
is no need to designate the variable as "FAST",
one simply needs to avoid having it be global,
static, or volatile.
----- Original Message -----
From: <Amit.Lubovsky@infineon.com>
To: <linux-mips@linux-mips.org>
Sent: Monday, March 31, 2003 6:45 PM
Subject: mips5kc - cpu registers
> Hi,
> is there a possibility to use cpu registers in the code (temporarily)
> instead of allocating
> automatic variables something like:
> func a()
> {
> FAST int, i, tmp;
> tmp = ...
> ...
> }
>
> as in vxWorks ?
>
> Thanks,
> Amit.
>
>
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Amit.Lubovsky@infineon.com, linux-mips@linux-mips.org
Subject: Re: mips5kc - cpu registers
Date: Mon, 31 Mar 2003 19:21:29 +0200 [thread overview]
Message-ID: <009401c2f7aa$0137f2a0$10eca8c0@grendel> (raw)
Message-ID: <20030331172129.PR-0J89uYvvIAwHt9mxxpCn7lBnB9QvChLgvgux1JXY@z> (raw)
In-Reply-To: 04C8EDC5AE3FD611ABE40002B39CF69B07F37F@ntah901e.savan.com
In general, gcc (and most other compilers)
will do this for you automatically if you enable
any reasonable level of optimization. There
is no need to designate the variable as "FAST",
one simply needs to avoid having it be global,
static, or volatile.
----- Original Message -----
From: <Amit.Lubovsky@infineon.com>
To: <linux-mips@linux-mips.org>
Sent: Monday, March 31, 2003 6:45 PM
Subject: mips5kc - cpu registers
> Hi,
> is there a possibility to use cpu registers in the code (temporarily)
> instead of allocating
> automatic variables something like:
> func a()
> {
> FAST int, i, tmp;
> tmp = ...
> ...
> }
>
> as in vxWorks ?
>
> Thanks,
> Amit.
>
>
next prev parent reply other threads:[~2003-03-31 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 16:45 mips5kc - cpu registers Amit.Lubovsky
2003-03-31 16:05 ` Juan Quintela
2003-03-31 17:21 ` Kevin D. Kissell [this message]
2003-03-31 17:21 ` Kevin D. Kissell
2003-04-01 0:37 ` Muthukumar Ratty
2003-04-01 0:37 ` Muthukumar Ratty
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='009401c2f7aa$0137f2a0$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=Amit.Lubovsky@infineon.com \
--cc=linux-mips@linux-mips.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