From: Michael Gschwind <mikeg@watson.ibm.com>
To: oliva@dcc.unicamp.br (Alexandre Oliva)
Cc: kenner@vlsi1.ultra.nyu.edu, gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: Proposal for new organization of gcc
Date: Thu, 08 Jan 1998 18:28:00 -0000 [thread overview]
Message-ID: <9801090228.AA32384@rios8.watson.ibm.com> (raw)
In-Reply-To: <orbtxm8pp2.fsf@amazonas.dcc.unicamp.br>
> <---- gcc-3.0.tar.gz ---->
> gcs-3.0/configure
> it picks up information from the various languages front-ends
> and builds Makefile that will build them all. It checks
> whether the bkend
>[etc]
> Comments? Improvements? Suggestions?
Sounds good to me... There should be a big tarball with all of this
and all the test stuff included -- I don't use g77, pascal etc., but
I'd be happy enough to install and test them if its only a make test
away...
m.
--
Michael K. Gschwind
IBM T.J. Watson Research Center phone (external): (914) 945-1675
PO Box 218 phone (internal): T/L 862-1675
Yorktown Heights, NY 10598 e-mail: mikeg@watson.ibm.com
next prev parent reply other threads:[~1998-01-08 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9801082336.AA26988@vlsi1.ultra.nyu.edu>
1998-01-08 16:24 ` Alexandre Oliva
1998-01-08 18:28 ` Michael Gschwind [this message]
1998-01-11 18:24 ` Richard Stallman
1998-01-11 18:58 ` Alexandre Oliva
1998-01-12 17:55 ` Richard Stallman
1998-01-13 4:31 ` Alexandre Oliva
1998-01-20 12:42 ` Richard Stallman
1998-01-20 14:54 ` Alexandre Oliva
1998-01-21 9:18 ` Richard Stallman
1998-01-22 1:45 ` Richard Earnshaw
1998-01-22 2:29 ` Alexandre Oliva
1998-01-22 4:12 ` Richard Earnshaw
1998-01-22 2:29 ` Alexandre Oliva
1998-01-23 14:48 ` Harvey J. Stein
1998-01-23 14:48 ` amylaar
[not found] <9801121156.AA07482@vlsi1.ultra.nyu.edu>
1998-01-12 4:09 ` Alexandre Oliva
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=9801090228.AA32384@rios8.watson.ibm.com \
--to=mikeg@watson.ibm.com \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=oliva@dcc.unicamp.br \
/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).