public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yotam Medini <yotamm@tmai.com>
To: law@cygnus.com, egcs@cygnus.com
Cc: brian_barrick@tmai.com
Subject: Re: egcs & gcc 2.8 ??
Date: Thu, 11 Dec 1997 10:52:00 -0000	[thread overview]
Message-ID: <199712111819.KAA02784@telaviv.tmai.com> (raw)

>     >  http://www.cygnus.com/egcs/egcs-1.0.html:
>     > 
>     >    egcs-1.0 also contains many improvements and features not found in
>     >    gcc-2.7 and even the soon to be released gcc-2.8 compilers.
>     > 
>     > Could someone please educate me about the relations between 
>     > egcs and gcc 2.8?
>   It's pretty simple.
>
>   egcs-1.0 is based on an early August snapshot of the gcc-2.8 development
>   sources with many of our own enhancements & bugfixes.
>
>   The current snapshots are based on the soon to be release gcc-2.8 (again
>   with our enhancements and bugfixes).
>
>   jeff

Many of egcs users, I believe, assume that a code 
compiled with egcs's gcc/g++ could be compiled eventually
with the official gcc-<l>.<m>.<n>.
Therefore, we would all like to help with early feedback on further 
gcc development.

So the questions are really:

  * How gcc's official release is determined.
  * What are the egcs features that will not make it
    into the next gcc release.
  * What is the expected time length for a bug-fix in some egcs snap-shot
    to propogate to the official gcc release.

Much thanks -- yotam

             reply	other threads:[~1997-12-11 10:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-11 10:52 Yotam Medini [this message]
1997-12-11 11:14 ` Jeffrey A Law
1997-12-11 16:11   ` Joe Buck
1997-12-11 20:29     ` Jeffrey A Law

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=199712111819.KAA02784@telaviv.tmai.com \
    --to=yotamm@tmai.com \
    --cc=brian_barrick@tmai.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    /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).