From: Andrew Haley <aph@redhat.com>
To: 이환희 <ad1984lee@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Can be gcc portable to architecture without indexed addressing mode?
Date: Wed, 17 Mar 2010 15:18:00 -0000 [thread overview]
Message-ID: <4BA09296.3070905@redhat.com> (raw)
In-Reply-To: <963a6961003162319l4c8f8504t42ddaf94d562287e@mail.gmail.com>
On 03/17/2010 06:19 AM, ì´í™˜í¬ wrote:
> Hello.
>
> I have to start to make some c compiler for my own cpu. This cpu has
> very simple core and has many limitations.
>
> I think that many of those limitations are evitable in source coding.
> But I cannot convince a few of them.
>
> Instructions of this cpu core have no indexed addressing mode like
> 'base' + 'offset'.
>
> This cpu can address memories only according to followings.
>
> immediate addressing
> indirect addressing with general registers
>
> I really want to know that gcc is portable on this core in spite of
> the limitation.
It is, but the generated code is going to be very poor.
Andrew.
next prev parent reply other threads:[~2010-03-17 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 7:51 이환희
2010-03-17 15:18 ` Andrew Haley [this message]
2012-08-01 11:57 Tim Rye
2012-08-01 13:08 ` Ian Lance Taylor
2012-08-01 14:54 ` Tim Rye
2012-08-01 15:02 ` Ian Lance Taylor
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=4BA09296.3070905@redhat.com \
--to=aph@redhat.com \
--cc=ad1984lee@gmail.com \
--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).