From: Bart Veer <bartv@redhat.com>
To: zhouhongtu@sina.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] GNU C for 8/16 bits CPU?
Date: Mon, 05 Feb 2001 05:39:00 -0000 [thread overview]
Message-ID: <200102051339.f15Dd3p14911@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <20010205121609.19125.qmail@sina.com>
>>>>> " " == zhouhongtu <zhouhongtu@sina.com> writes:
> Could I get the GNU C tools for 8/16 bits CPU? for example
> 80188. If could ,how can I get?
> ______________________________________
The internal architecture of gcc is not well-suited to supporting 8 or
16 bit processors. A small number of such processors are supported,
e.g. I believe the mn10200 is 16-bit, and there is an 8-bit port for
AVR microcontrollers. I am not aware of any port to the 80188: the
use of segmented memory rather than a flat address space, and hence
the need for various memory models, makes it difficult to support any
x86 processor prior to the 386.
For further information check the gcc web pages and mailing lists,
http://gcc.gnu.org/
Bart
prev parent reply other threads:[~2001-02-05 5:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 4:06 zhouhongtu
2001-02-05 5:39 ` Bart Veer [this message]
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=200102051339.f15Dd3p14911@sheesh.cambridge.redhat.com \
--to=bartv@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=zhouhongtu@sina.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).