From: Sriharsha <sriharsha.v@redpinesignals.com>
To: sashti srinivasan <svasn_tcpip@yahoo.co.in>
Cc: gcc-help@gcc.gnu.org
Subject: Re: custom CPU porting : guidance please
Date: Mon, 20 Dec 2004 06:17:00 -0000 [thread overview]
Message-ID: <41C66F74.1050706@redpinesignals.com> (raw)
In-Reply-To: <20041219095738.63990.qmail@web8507.mail.in.yahoo.com>
sashti srinivasan wrote:
>Hello,
> I like to port complete gcc tool-chain including
>gas,gasp,ld,binutils... to a custom CPU. May I
>request the mailing list the following:
>
> (1) I intend doing it as a single man during
>leisure time. Please suggest me in approximately how
>much time (in terms of hours) can I expect this port
>to complete.
>
>
Difficult to suggest how long it would take. It depends on a lot of
things like your knowledge and experience with compilers, C language and
computer architecture, the architecture of the Processor and the
complexity involved. If it is similar to the standard processors, then,
the port is a fairly simple one.
> (2) Where can I find the documentation and other
>resources regarding how to do the port.
>
>
An excellant link is:
http://www.le-hacker.org/hacks/projects/microprocessor/compiler.html
And ofcourse, you always have the colossal documentation from gnu site.
http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc.html or something similar
Finally, last but not the least..... try this:
http://gcc.gnu.org/readings.html where you find links to lots of stuff::::
Of special interest among them is:
Porting GCC for Dunces by Hans-Peter Nilsson.
> (3) The goal is to port the tool-chain and build
>operating systems like RTEMS, Linux etc. for this CPU.
>
>
A good idea.
> I will be very thankful to receive some broad
>suggestions.
>
>
You are always welcome.
Sriharsha
--
*****************************
* Sriharsha Vedurmudi
* Software Engineer
*
* Redpine Signals Inc.
* Gate #395, Plot 87,88
* Sagar Society, Road #2,
* Banjara Hills,
* Hyderabad - 500 034
* www.redpinesignals.com
*
* +91-40-23559911 (Office)
* +91-98851-37338 (Mobile)
*****************************
next prev parent reply other threads:[~2004-12-20 6:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-18 9:54 Ancient Fortran, help please Bud Davis
2004-12-18 19:22 ` Benjamin Joseph
2004-12-19 0:35 ` Bud Davis
2004-12-19 3:48 ` Benjamin Joseph
2004-12-19 9:57 ` custom CPU porting : guidance please sashti srinivasan
2004-12-20 6:17 ` Sriharsha [this message]
2004-12-23 18:25 ` sashti srinivasan
2004-12-23 18:33 ` 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=41C66F74.1050706@redpinesignals.com \
--to=sriharsha.v@redpinesignals.com \
--cc=gcc-help@gcc.gnu.org \
--cc=svasn_tcpip@yahoo.co.in \
/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).