From: "gabriele" <gabriele@caracausi.it>
To: gcc@gcc.gnu.org
Subject: Passes for a new porting
Date: Mon, 31 Mar 2003 13:36:00 -0000 [thread overview]
Message-ID: <20030331083807.19931.qmail@mx5.aruba.it> (raw)
Hello All!
This question is for people who made a porting to a new target.
Probably this is a stupid question but I have this doubt.
I'm working on the porting of a new target and I've read many other portings
of architectures similar to mine.
I've looked that many of these portings are very complex (file .md) and this
thing scared me but probably these are the result of many months or years of
hard working.
So if I want to port to a new target initially have I to refear only to
standard documents (i.e. original GCC documentation) without scaring me of
the complexity of existent portings?
This strategy'll direct me to success in my project?
Thanks all.
Gabriele Caracausi
Palermo (Italy)
reply other threads:[~2003-03-31 8:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030331083807.19931.qmail@mx5.aruba.it \
--to=gabriele@caracausi.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).