Date:	Sun, 5 Aug 2001 10:36:21 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Test binaries of gcc-3.0.1 20010802 (prerelease)
In-Reply-To:	<Pine.LNX.4.10.10108031753590.15648-100000@acp3bf>
Message-ID:	<Pine.SUN.3.91.1010805103602.10001P-100000@is>
MIME-Version:	1.0
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

On Fri, 3 Aug 2001, Hans-Bernhard Broeker wrote:

> > 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.

This shouldn't have caused Gas to fail, for 3 reasons:

  - the 64K-line limit causes trouble during link, not assembly;

  - the limit only exists as far as the debug info is concerned, it is
    not relevant to generating code;

  - this problem was made non-fatal long ago (in Binutils 2.8.1, I
    think): the linker prints the warning and continues linking, but
    stops generating source line info in the debug records.

FWIW, I hit the 64K-line limit all the time when I build GDB, but a
healthy gdb.exe is produced anyway.

- Raw text -