From: pavenis AT lanet DOT lv
To: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>,
        djgpp-workers AT delorie DOT com
Date: Mon, 6 Aug 2001 11:43:53 +0300
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Test binaries of gcc-3.0.1 20010802 (prerelease)
Message-ID: <3B6E82F9.30336.1AB49F@localhost>
References: <3B6AEF74 DOT 318 DOT FCAC74 AT localhost>
In-reply-to: <Pine.LNX.4.10.10108031753590.15648-100000@acp3bf>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

On 3 Aug 2001, at 17:55, Hans-Bernhard Broeker wrote:

> On Fri, 3 Aug 2001 pavenis AT lanet DOT lv wrote:
> 
> > One more problem: 
> > 
> > It seems that -gcoff support have suffered from too serious bitrot:
> > 	trying to run LAPACK tests with this gcc version run into trouble
> > 	when GAS (binutils-2.11.2 and also some other recent versions) 
> > 	failed when -g was specified (with -gstabs+ all was Ok)
> 
> Failed how? One likely reason migth be that LAPACK could easily hit the
> 64K source lines limit imposed by COFF debugging info, I guess.
> 

I submitted related bug report to GCC GNATS (it's also posted to 
djgpp-workers as I added this address to CC:). 

Shortly: it's nothing related to 64K source lines limits. Simply f771.exe
   generates .def lines (COFF debugging info) which causes GAS to fail

Andris