From: Joe Buck <jbuck@racerx.synopsys.com>
To: stumeikle@hotmail.com (Stu Meikle)
Cc: gcc@gcc.gnu.org
Subject: Re: porting
Date: Thu, 21 Sep 2000 14:37:00 -0000 [thread overview]
Message-ID: <200009212136.OAA23141@racerx.synopsys.com> (raw)
In-Reply-To: <F271RDT6Z3LstPGtPrP0000070d@hotmail.com>
> (1) what platforms is Gcc known to have been successfully ported to ? (and
> could you put it on the web page please), and
This is a question that it is hard to give a precise answer to.
gcc has been ported to a vast number of platforms, including a number
of platforms that no longer even exist. The less-used platforms
tend to suffer from bit rot and so cannot be assumed to work.
On the page http://gcc.gnu.org/gcc-2.95/regress.html you can find a list
of the platforms for which gcc 2.95.x has been thoroughly tested.
However, there are many more backends than are listed there. Cygnus and
other companies provide support for many GCC embedded-platform backends
for their customers, so the code for them can considered to be reasonably
solid for popular processors.
For more information on what backends exist and what the options for
controlling them are, see the "Hardware Models and Configurations"
section of the GCC manual, online at
http://gcc.gnu.org/onlinedocs/gcc_2.html#SEC18
> (2) in the case that I were to develop a new hardware platform, what would
> be the best way to go about porting Gcc to that platform ? Is it something
> which the FSF/GNU would want to take charge of ? or, if I were to do it
> myself what coding conventions etc should I follow?
It would be up to you or your organization to do the port, or you could
hire someone to do it for you. See http://gcc.gnu.org/contribute.html
for more on the requirements for contributions.
Please also read http://gcc.gnu.org/contributewhy.html .
prev parent reply other threads:[~2000-09-21 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-21 3:03 porting Stu Meikle
2000-09-21 14:37 ` Joe Buck [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=200009212136.OAA23141@racerx.synopsys.com \
--to=jbuck@racerx.synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=stumeikle@hotmail.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).