From: "Filippo Basso" <filippo@zirak.it>
To: <gcc@gcc.gnu.org>
Subject: porting gcc
Date: Thu, 15 Feb 2001 08:41:00 -0000 [thread overview]
Message-ID: <006a01c0976e$341bae80$73c323d4@zirak.it> (raw)
Hi, I'm filippo from Italy,
and I'm trying to port Linux 2.0.38 under a DSP-multiRISC architecture, with the uCLinux fellows...
Now, Alessandro Rubini told me that it will be better to have first GCC ported to this architecture...
Is it possible ?
Where do I have to start from ?
Is there some guy that have some time to ask stupid questions ?
(n.b. for this processor, I have an ansi-C compiler (well, a quasi-ansi), an assembler, and a linker,... some tools. I need only to
do the scalar port (using the DSP, the multiRISC I'll think the day after ! ;-))
really thanks,
phy
next reply other threads:[~2001-02-15 8:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 8:41 Filippo Basso [this message]
2001-02-15 9:50 ` Fergus Henderson
-- strict thread matches above, loose matches on Subject: below --
2008-10-20 10:20 Aurélien Buhrig
2008-10-20 19:34 ` Ian Lance Taylor
2008-03-12 6:11 Porting gcc Schmave
2008-03-12 6:15 ` Ben Elliston
2004-06-04 15:24 Porting GCC Gyle Yearsley
2004-06-02 16:49 Gyle Yearsley
2004-06-03 15:38 ` Richard Sandiford
2004-05-21 13:09 Porting gcc Mile Davidovic
2004-05-21 13:43 ` Dave Korn
2003-08-13 11:15 Petar Penchev
2003-08-13 16:07 ` Ben Elliston
2002-10-22 9:53 porting gcc Grégoire Dooms
2002-10-22 9:56 ` Grégoire Dooms
2002-10-22 14:40 ` Mike Stump
2002-10-22 14:43 ` Andrew Haley
2002-10-22 15:16 ` Michael Matz
2002-10-22 15:27 ` Svein E. Seldal
2002-10-22 18:02 ` Mike Stump
2002-10-23 10:05 ` Andrew Haley
2002-10-22 15:50 ` Denis Chertykov
2001-02-01 2:37 porting GCC Krzysztof Matula
2001-02-01 3:10 ` Richard Earnshaw
2001-02-02 3:43 ` Krzysztof Matula
2001-02-02 4:00 ` Richard Earnshaw
2001-02-02 6:07 ` Krzysztof Matula
2001-02-02 7:08 ` Richard Earnshaw
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='006a01c0976e$341bae80$73c323d4@zirak.it' \
--to=filippo@zirak.it \
--cc=gcc@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).