From: "Thomas Bushnell, BSG" <tb+usenet@becket.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] splitting the compiler
Date: Thu, 28 Feb 2002 16:53:08 +0000 [thread overview]
Message-ID: <87bse9h7ni.fsf@becket.becket.net> (raw)
In-Reply-To: <vi4u1s163jy.fsf@blue.cs.yorku.ca>
ozan s yigit <oz@blue.cs.yorku.ca> writes:
> "Thomas Bushnell, BSG" <tb+usenet@becket.net> writes:
>
> > I'm pretty familiar with GCC internals, and it's pretty darn
> > portable. But perhaps there's a whole level of portability I'm
> > missing.
>
> original poster meant retargeting (i think). with (say) lcc, all one has
> to worry about is a relatively straight-forward code generator. a student
> targeted it for ns32000 in about a week. i would expect no more time for
> 8c, but estimate three to six months for gcc.
Hrm, I retargeted GCC (back in the days of version 1) for the old
Clipper chip in about a month.
Thomas
next prev parent reply other threads:[~2002-02-28 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 15:32 paurea
2002-02-28 10:13 ` Thomas Bushnell, BSG
2002-02-28 16:02 ` ozan s yigit
2002-02-28 16:53 ` Thomas Bushnell, BSG [this message]
2002-03-04 10:03 ` ozan s. yigit
2002-03-04 17:04 ` Thomas Bushnell, BSG
2002-02-28 9:04 forsyth
2002-02-28 9:42 ` Matt H
2002-02-28 17:21 forsyth
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=87bse9h7ni.fsf@becket.becket.net \
--to=tb+usenet@becket.net \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).