From: Mike Stump <mrs@apple.com>
To: "Grégoire Dooms" <dooms@student.info.ucl.ac.be>
Cc: gcc@gcc.gnu.org
Subject: Re: porting gcc
Date: Tue, 22 Oct 2002 14:40:00 -0000 [thread overview]
Message-ID: <0125F728-E5F0-11D6-802D-000393941EE6@apple.com> (raw)
In-Reply-To: <20021022125558.BF06A22213B@yhwh>
On Tuesday, October 22, 2002, at 05:55 AM, Grégoire Dooms wrote:
> I've read all the documentation (Passes, Machine Description, ...) and
> the
> AVR (other 8bit uc) files (.md .c .h).
>
> What should I do now?
File your paperwork, and port it.
> Is it possible to incrementally write those files ?
Yes. I find it convenient to copy some working port, and then modify
it until done. I maintained a working compiler that generated
progressively more correct code. This why I would tell how close I
was, and if the compiler started to not work, I knew it was related to
the last edit, thus shortening my search space. Sometimes the way sin
which the compiler can fail are non-obvious, but being able to fall
back on the temporal information was handy.
> Is there a document explaining that process?
Just what's on our web site.
> Who should I ask about a few not-understood stuff in the AVR files?
I'd just ignore it, maybe the trickery won't be needed in your port.
Or, maybe you'll understand it better when you have 90% of the easy
stuff done.
next prev parent reply other threads:[~2002-10-22 18:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 9:53 Grégoire Dooms
2002-10-22 9:56 ` Grégoire Dooms
2002-10-22 14:40 ` Mike Stump [this message]
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
-- 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
2001-02-15 8:41 porting gcc Filippo Basso
2001-02-15 9:50 ` Fergus Henderson
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=0125F728-E5F0-11D6-802D-000393941EE6@apple.com \
--to=mrs@apple.com \
--cc=dooms@student.info.ucl.ac.be \
--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).