From: Ian Lance Taylor <iant@google.com>
To: Mohamed Shafi <shafitvm@gmail.com>
Cc: GCC <gcc@gcc.gnu.org>
Subject: Re: About feasibility of implementing an instruction
Date: Thu, 02 Jul 2009 19:46:00 -0000 [thread overview]
Message-ID: <m3ljn6rhqp.fsf@google.com> (raw)
In-Reply-To: <ba0bd44d0907012159i1ba3d230sdfdb88f6201b8568@mail.gmail.com> (Mohamed Shafi's message of "Thu\, 2 Jul 2009 10\:29\:15 +0530")
Mohamed Shafi <shafitvm@gmail.com> writes:
> I just want to know about the feasibility of implementing an
> instruction for a port in gcc 4.4
> The target has 40 bit register where the normal load/store/move
> instructions will be able to access the 32 bits of the register. In
> order to move data into the rest of the register [b32 to b39] the data
> has to be stored into a 32bit memory location. The data should be
> stored in such a way that if it is stored for 0-7 in memory the data
> can be moved to b32-b39 of a even register and if the data in the
> memory is stored in 16-23 of the memory word then it can be moved to
> b32-b39 of a odd register. Hope i make myself clear.
>
> Will it be possible to implement this in the gcc back-end so that the
> particular instruction is supported?
In general, the gcc backend can do anything, so, yes, this can be
supported. It sounds like this is not a general purpose register, so I
would probably do it using a builtin function. If you need to treat it
as a general purpose register (i.e., the register is managed by the
register allocator) then you will need a secondary reload to handle
this.
Ian
next prev parent reply other threads:[~2009-07-02 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 4:59 Mohamed Shafi
2009-07-02 19:46 ` Ian Lance Taylor [this message]
2009-08-15 7:31 ` Mohamed Shafi
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=m3ljn6rhqp.fsf@google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=shafitvm@gmail.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).