From: wkt@minnie.tuhs.org (Warren Toomey)
Subject: [pups] Re: GCC
Date: Sun, 20 Jan 2002 07:19:08 +1000 (EST) [thread overview]
Message-ID: <200201192119.g0JLJ8i00979@minnie.tuhs.org> (raw)
In-Reply-To: <85d706iv5h.fsf@junk.nocrew.org> from Lars Brinkhoff at "Jan 19, 2002 09:48:10 am"
In article by Lars Brinkhoff:
> norman at nose.cs.utoronto.ca writes:
> > I would probably use lcc as a cross-compiler myself, after writing
> > or snitching a code generator of course.
>
> bwc at borf.com writes:
> > I got Dennis' sixth edtion compiler to compile not long ago.
> > My advice would be to start there.
>
> How about the 2.11BSD compiler?
The next question is, why to do this, and for which operating system(s)?
If it's to get an ANSI C compiler, or some extra performance, then I
can see the point. If it's to ditch a `contaminated' compiler, then
I can see a few difficulties, especially if the target is 2.11BSD
The 2.11BSD linker knows an awful lot about overlays, and any replacement
would need to do the same.
Anway, that's my $0.02. I thought about porting lcc to 2.11BSD ages ago,
but I've never had the time to do it.
Cheers,
Warren
next prev parent reply other threads:[~2002-01-19 21:19 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <no.id>
2002-01-18 6:53 ` Aaron J. Grier
2002-01-18 7:07 ` Wilko Bulte
2002-01-18 9:06 ` Lars Brinkhoff
2002-01-18 12:44 ` Warren Toomey
2002-01-18 14:49 ` Bill Gunshannon
2002-01-18 15:31 ` Lars Brinkhoff
2002-01-18 19:00 ` Johnny Billquist
2002-01-18 21:54 ` Jonathan Engdahl
2002-01-19 8:48 ` Lars Brinkhoff
2002-01-19 21:19 ` Warren Toomey [this message]
2002-01-18 18:06 ` Aaron J. Grier
2002-01-30 1:57 ` [TUHS] Re: Porting Unix v6 to i386 Aaron J. Grier
2002-01-30 9:18 ` P.A.Osborne
2002-01-30 18:00 ` Sven Dehmlow
2002-01-30 19:50 ` Johnny Billquist
2002-01-30 21:40 ` Michael Davidson
2002-01-31 10:26 ` P.A.Osborne
2002-01-31 18:51 ` Johnny Billquist
2002-02-01 10:27 ` P.A.Osborne
2002-01-31 19:04 ` Mike Haertel
2002-01-30 19:52 ` Mike Haertel
2002-01-30 20:54 ` M. Warner Losh
2002-01-30 22:47 ` Greg Lehey
2002-03-03 12:51 ` Cyrille Lefevre
2002-03-03 20:14 ` Peter Jeremy
2002-03-03 20:46 ` Tim Shoppa
2002-03-03 21:07 ` Peter Jeremy
2002-01-31 9:18 ` Lauri Aarnio
2002-01-31 11:00 ` P.A.Osborne
2002-01-31 16:09 ` Sven Dehmlow
2002-01-31 18:45 ` Lauri Aarnio
2002-02-01 0:42 ` Greg Lehey
2002-02-04 22:12 ` Michael Davidson
2002-02-05 10:42 ` P.A.Osborne
2002-02-06 16:36 ` Jeffrey S. Sharp
2002-02-07 10:23 ` P.A.Osborne
2002-01-30 22:44 ` Greg Lehey
2002-02-14 22:30 ` Aaron J. Grier
2002-02-15 3:08 ` Peter Jeremy
2002-02-15 8:08 ` Lars Brinkhoff
2002-01-19 16:22 [pups] Re: GCC Davidson, Steve
-- strict thread matches above, loose matches on Subject: below --
2002-01-19 14:54 SHOPPA
2002-01-19 15:12 ` Johnny Billquist
2002-01-18 22:29 bwc
2002-01-19 0:08 ` Bill Gunshannon
2002-01-18 22:13 norman
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=200201192119.g0JLJ8i00979@minnie.tuhs.org \
--to=wkt@minnie.tuhs.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 NNTP newsgroup(s).