From: Oleg Endo <oleg.endo@t-online.de>
To: "eljedi ." <eljedi@gmail.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GCC port
Date: Wed, 20 Nov 2013 19:47:00 -0000 [thread overview]
Message-ID: <1384975039.2438.109.camel@yam-132-YW-E178-FTW> (raw)
In-Reply-To: <CANW-Qq6j7dEX47o=M3xjK=bLw6CkjVQYy36B0zj6tZcbhBtjZQ@mail.gmail.com>
On Wed, 2013-11-20 at 19:25 +0100, eljedi . wrote:
> Thank you Jonathan for the quick reply.
>
> About the CPU I mentioned, do you think it can be done? (its a 16bits,
> and I read gcc works fine for 32bits processors with 32bits registers,
> more than one).
Yes, it can be done.
For example, AVR is also < 32 bits and it works.
Cheers,
Oleg
next prev parent reply other threads:[~2013-11-20 19:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 18:22 eljedi .
2013-11-20 18:25 ` Jonathan Wakely
2013-11-20 19:17 ` eljedi .
2013-11-20 19:47 ` Oleg Endo [this message]
2013-11-21 8:39 ` eljedi .
2013-11-21 10:56 ` David Brown
2013-11-21 11:41 ` Brian Drummond
2013-11-21 13:15 ` David Brown
2013-11-21 17:51 ` Jeff Law
2013-11-22 11:52 ` David Brown
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=1384975039.2438.109.camel@yam-132-YW-E178-FTW \
--to=oleg.endo@t-online.de \
--cc=eljedi@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@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).