X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10411100500.AA96556@clio.rice.edu>
Subject: Re: gcc-3.4 and option -mcpu
To: djgpp-workers AT delorie DOT com
Date: Tue, 9 Nov 2004 23:00:00 -0600 (CST)
In-Reply-To: <200410291617.i9TGHo6B022589@speedy.ludd.ltu.se> from "ams@ludd.ltu.se" at Oct 29, 2004 06:17:50 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavis-20030616-p6 at mail.rice.edu
X-DCC--Metrics: handler6.mail.rice.edu 1066; Body=1 Fuz1=1 Fuz2=1
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> According to DJ Delorie:
> > Unless there's a compelling reason to require 2.*, let's drop it.
> > We've had plenty of time to get 3.* working for our purposes.
> 
> Personally _I_'d like to continue to use 2.95 for DJGPP.

Myself also.  It seems 2.95 always generates much smaller code, and
in many cases it's also turned out to be the same speed or marginally
faster.  But I could say that about 2.8.1 in some cases too...

> But if there's only me, I'll accept having to upgrade.

It would be nice if there were an alterate file or a readme to at
least give a path to do your own hack to fix it without reinventing
it each time