Date: Fri, 29 Oct 1999 17:33:42 +0200 From: Marc Lehmann To: PGCC Mailing List Subject: Re: Does PGCC get updated on each release? Message-ID: <19991029173342.A8224@cerebro.laendle> Mail-Followup-To: PGCC Mailing List References: <19991029053010 DOT EXNH5192 DOT mail DOT rdc1 DOT il DOT home DOT com AT mercury DOT snydernet DOT lan> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <19991029053010.EXNH5192.mail.rdc1.il.home.com@mercury.snydernet.lan>; from Steve Snyder on Fri, Oct 29, 1999 at 12:30:13AM -0400 X-Operating-System: Linux version 2.2.12 (root AT cerebro) (gcc version 2.95.1 19990816 (release)) Sender: Marc Lehmann Reply-To: pgcc AT delorie DOT com X-Mailing-List: pgcc AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Fri, Oct 29, 1999 at 12:30:13AM -0400, Steve Snyder wrote: > Is the code in the gcc-->pgcc diff actively being worked on, or is the > same patch code applied to each new version of egcs/gcc as they are > released? With former releases I used (almost) the same diff for minor releases, sicne I developed using the development snapshots of the compiler and didnīt want to backport fixes (that might break it). Since I havenīt had time to jump on the current gcc snapshots, I _do_ work on the current diff. But as al you know, I was/am/will be seriously busy, so the only changes you can expect in 2.95.2 are two bug-fixes, some warning patch and a disabled -fcompare-elim. > (Obviously the patch files are modified to handling differing version > strings, etc. It is more the code generation that I have in mind.) In this and all former (minor) releases, no ground-breaking things have been added. -- -----==- | ----==-- _ | ---==---(_)__ __ ____ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / pcg AT opengroup DOT org |e| -=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |