9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] Go/Inferno toolchain (Was: comment and newline in define)
Date: Sat, 26 Jun 2010 07:19:59 +0200	[thread overview]
Message-ID: <efe89fa19cbbd3c20630c5f5dfea4b46@proxima.alt.za> (raw)
In-Reply-To: <AANLkTinCJcMZaUvVKjPjpQDmDlHcPiAFUIyREHgo4TKd@mail.gmail.com>

> The [568]c compilers in the Go tree are based on the Inferno/Plan 9
> compilers. Did something change?

Yes, they added ELF, didn't they?  And they used GCC to compile
everything, which is the bit I've been trying to consolidate since
more or less the very beginning.  The objective of the consolidation
is three-fold: (1) upgrade the Plan 9 toolchain to whatever fresh and
progressive features the Go toolchain provides, including targetting
ELF (and 6c, not to discounted); (2) port Go to Plan 9 and (3) add to
plan9port the ability the Go toolchain (as an alternative to GCC) for
program development.

There's a fourth objective, but it may be above my skill level, which
is to port all the other Plan 9 and/or Inferno architectures into the
consolidated toolchain.  Also, one needs to consolidate the linker and
libmach in some fashion and, lastly, somehow blend in binutils, GCC
and GDB into the project.  Although the decision by the GCC developers
to allow C++ code into the GCC codebase, as reported in slashdot, puts
a bit of a spanner in the works.

It seems a little bit more than the average summer of code endeavour,
but I'm not discouraging anyone who may want to tackle any of the
above.  It would be nice if I was made aware of others who may be
interested.  Right now, I'm catching up with work I did late December
last year, before it gets lost, buried or uselessly out of date.

++L




  parent reply	other threads:[~2010-06-26  5:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25 15:35 [9fans] comment and newline in define lucio
     [not found] ` <AANLkTilhVWAu8htoIL903rtMK1z9Sw88pSfEASawc5Xi@mail.gmail.com>
2010-06-26  0:50   ` Christopher Nielsen
2010-06-26  0:58     ` erik quanstrom
2010-06-26  4:18       ` Rob Pike
2010-06-26  6:15         ` Christopher Nielsen
2010-06-26  5:19     ` lucio [this message]
2010-06-26  6:46       ` [9fans] Go/Inferno toolchain (Was: comment and newline in define) Christopher Nielsen
2010-06-26  9:26         ` [9fans] Go/Inferno toolchain (Was: comment and newline in lucio
2010-06-26 10:34           ` erik quanstrom
2010-06-26 11:00             ` lucio
2010-06-28 22:03           ` Eric Van Hensbergen
2010-06-29 17:24             ` Rob Pike
2010-06-29 17:31               ` Devon H. O'Dell
2010-06-29 17:36               ` Francisco J Ballesteros
2010-06-29 17:48                 ` Francisco J Ballesteros
2010-06-29 18:02                   ` Jack Johnson
2010-06-29 18:10               ` Eric Van Hensbergen
2010-06-29 18:12                 ` Francisco J Ballesteros
2010-06-29 20:30                   ` Eric Van Hensbergen
2010-06-29 18:32                 ` erik quanstrom
2010-06-29 20:45                   ` Eric Van Hensbergen
2010-06-29 20:52                     ` erik quanstrom
2010-06-29 21:03                       ` ron minnich
2010-06-29 21:36                         ` Steve Simon
2010-06-29 21:54                         ` Charles Forsyth
2010-06-30  9:25                           ` Lucio De Re
2010-06-29 22:35                         ` cinap_lenrek
2010-06-29 23:00                         ` Russ Cox
2010-06-30  8:17                           ` Lucio De Re
2010-06-29 21:15                       ` Devon H. O'Dell
2010-06-29 21:27                         ` ron minnich
2010-06-26  7:37       ` [9fans] Go/Inferno toolchain (Was: comment and newline in define) Ethan Grammatikidis

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=efe89fa19cbbd3c20630c5f5dfea4b46@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.net \
    /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).