Mail Archives: pgcc/1999/04/26/15:17:14
On Sun, Apr 25, 1999 at 10:58:51PM +0000, Jason wrote:
> [Announcement omitted.]
>
> The question that's on my mind is: what does this mean for pgcc in terms of
> its relationship to egcs/gcc?
Oh, the faq entry on this is still quite correct. In the old gcc times, no
merging was possible. Full Stop.
With egcs, the door to to mergings (intelligent ones) was opened. This
means that successful pgcc features (not all of it are) migrate into
egcs. The difference between egcs and gcc has decreased steadily with
regards to code quality and features.
There are no strict guidelines on how the releases/snaoshots process for
egcs will look like in the future, thats the steering committee's job in
the coming weeks/months.
However, taking over gcc maintainership means that the egcs development
and releasde style will be carried over and applied to gcc.
> Will the optimizations be merged directly into the new source tree,
> or will it remain separate, distributed as patches to the egcs (well,
> actually gcc now) source? Has any of this even been determined yet? :)
It will stay seperate as long as it still is useful! At the day where
egcs is as good as pgcc in optimizing I will stop maintaining it ;) While
this might not happen anytime soon, the difference between egcs and pgcc
is decreasing as more and more pgcc features are also available (or even
better implemented) in egcs.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg AT goof DOT com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
- Raw text -