From: Andris Pavenis <pavenis AT latnet DOT lv>
To: djgpp-workers AT delorie DOT com
Subject: Binutils bug causes GCC bootstrap comparision failures
Date: Thu, 5 Jun 2003 23:34:12 +0300
User-Agent: KMail/1.5.2
MIME-Version: 1.0
Content-Type: Multipart/Mixed;
  boundary="Boundary-00=_El63+0Vn8bYDNpv"
Message-Id: <200306052334.12918.pavenis@latnet.lv>
Reply-To: djgpp-workers AT delorie DOT com


--Boundary-00=_El63+0Vn8bYDNpv
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Found that in some cases GAS (for example from bnu213b.zip) put's random byte
at end of .comment section, which causes bootstrap comparisson failure of 
current CVS versions of GCC. I have met this problem only with DJGPP native 
binutils. Linux to DJGPP cross-binutils does not show this behaviour.

Assembler source file attached.

Simple script to reproduce the problem:

#! /bin/sh
as mbchar.s -o mbchar.o1
as mbchar.s -o mbchar.o2
cmp mbchar.o1 mbchar.o2

This problem appears rather seldomly, as this was only file which failed 
comparrision test.

Andris

--Boundary-00=_El63+0Vn8bYDNpv
Content-Type: text/plain;
  charset="us-ascii";
  name="mbchar.s"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="mbchar.s"

	.file	"mbchar.c"
	.section	.debug_abbrev,""
Ldebug_abbrev0:
	.section	.debug_info,""
Ldebug_info0:
	.section	.debug_line,""
Ldebug_line0:
	.section .text
Ltext0:
Letext0:
	.section	.debug_abbrev,""
	.byte	0x0
	.ident	"GCC: (GNU) 3.4 20030604 (experimental)"

--Boundary-00=_El63+0Vn8bYDNpv--