public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alan Lehotsky <qsmgmt@earthlink.net>
To: redriver jiang <jiang.redriver@gmail.com>, gcc@gcc.gnu.org
Subject: Re: Is it possible to port GCC backend to a architecture with very   	limited hard registers?
Date: Wed, 17 Mar 2010 14:10:00 -0000	[thread overview]
Message-ID: <11825351.1268834467283.JavaMail.root@elwamui-muscovy.atl.sa.earthlink.net> (raw)

Almost certainly you will run into severe problems in the reload phase.

You might also profitably study the ip2k port.  This is a ALU machine, but it does have multiple
address registers.


-----Original Message-----
>From: redriver jiang <jiang.redriver@gmail.com>
>Sent: Mar 17, 2010 8:55 AM
>To: gcc@gcc.gnu.org
>Subject: Is it possible to port GCC backend to a architecture with very  	limited hard registers?
>
>Hi all,
>
>Right now I attempts to port the GCC backend to a MCU with very
>limited hard registers: only one 8 bit ACC reg, one 16 bit base reg
>for addressing, one stats reg.
>I searched the GCC backend porting, and seems 68HC1X has the similar
>scene, but it use many "ram simulated" register. I wonder that if it
>is possbile to provided thislimited 3 register to GCC bankend, and let
>all 16bit(HImode), 32bit(SImode) operands spilled to stack.
>
>Thanks!
>
>Redriver

             reply	other threads:[~2010-03-17 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 14:10 Alan Lehotsky [this message]
2010-03-17 15:01 ` Dave Hudson
  -- strict thread matches above, loose matches on Subject: below --
2010-03-17 14:01 redriver jiang
2010-03-17 18:31 ` Ian Lance Taylor
2010-03-18 13:43   ` redriver jiang

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=11825351.1268834467283.JavaMail.root@elwamui-muscovy.atl.sa.earthlink.net \
    --to=qsmgmt@earthlink.net \
    --cc=apl@alum.mit.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=jiang.redriver@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).