X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
From:	<ams AT ludd DOT ltu DOT se>
Message-Id:	<200409301704.i8UH4nUu020036@speedy.ludd.ltu.se>
Subject:	Re: ANNOUNCE: DJGPP port of GCC-3.4.2
In-Reply-To:	<200409102121.19881.pavenis@latnet.lv> "from Andris Pavenis at Sep
	10, 2004 09:21:19 pm"
To:	Andris Pavenis <pavenis AT latnet DOT lv>
Date:	Thu, 30 Sep 2004 19:04:49 +0200 (CEST)
CC:	DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
X-Mailer:	ELM [version 2.4ME+ PL78 (25)]
MIME-Version:	1.0
X-ltu-MailScanner-Information:	Please contact the ISP for more information
X-ltu-MailScanner:	Found to be clean
X-MailScanner-From:	ams AT ludd DOT ltu DOT se
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

I'm CCing djgpp-workers too.

According to Andris Pavenis:
> On Friday 10 September 2004 20:53, you wrote:
> > In article <200409101743 DOT i8AHhRmY028387 AT delorie DOT com> Andris Pavenis 
> <pavenis AT latnet DOT lv> wrote:
> > > Note for users of C++ IO classes fstream, ifstream, ofstream
> > > ============================================================
> > >
> > > There is a regression against GCC versions 2.95.3 and
> > > earlier: Member functions tellp(), tellg(), seekp() and seekg()
> > > are broken when stream is opened not in binary mode. If You are going
> > > to use any similar functions You must open stream in binary mode.
> >
> > Perhaps you should add that g++ generates opcodes for 486 or later
> > (i. e. doesn't support 386s) unless that has been corrected?
> 
> I'm not sure, but as far as I understand, it could possibly work for 386, if 
> rebuilt from sources for i386-pc-msdosdjgpp. 

Do I understand you correctly that you know that your gpp package
doesn't work on 386s? "Work" here means that the compiler _and_ the
executables it builds do run on a 386. (I know that some older version
didn't make workable 386 executables.)

No, I misunderstood something:
	Then I guess we don't know if it does work or not. But 1 below
	should be considered.

Yes, that's what you're saying:
	Well, IMO:
	1. You really really really should point out that things built
	   with gpp only is for 486 (or Pentium or whatever) or later.

	2. Shouldn't it be compiled for i386-pc-msdosdjgpp then so
	   that it potentially does work 386s?


If the bug still is in gpp even when built for i386-pc-msdosdjgpp,
then we have to wait to get it fixed, but 1 still applies. Plus we
might need to change some texts which say "DJGPP requires at least a
386" adding ", 486 (or whatever) for C++ programs".


Right,

						MartinS

- Raw text -