This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
other/2775: avr.h CVS corruption
- To: gcc-gnats at gcc dot gnu dot org
- Subject: other/2775: avr.h CVS corruption
- From: Joseph Myers <jsm28 at cam dot ac dot uk>
- Date: Tue, 08 May 2001 17:11:23 +0000
- Cc: jsm28 at cam dot ac dot uk
>Number: 2775
>Category: other
>Synopsis: avr.h CVS corruption
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue May 08 10:16:02 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 3.0 20010506 (prerelease)
>Organization:
none
>Environment:
System: Linux digraph 2.2.19 #1 Wed Mar 28 16:01:38 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib --disable-libgcj
>Description:
As reported to overseers on 17 April, but not yet fixed:
/cvs/gcc/gcc/gcc/config/avr/avr.h,v seems to have become corrupted, as
shown by checksum errors when updating. The current revision is OK, but
diffs between 1.19 and 1.20 show a series of NUL characters that weren't
part of a correct 1.19 (as found in the last snapshot, etc.):
(cut-and-pasted; the second part of the diff is correct):
[gccadmin@sourceware avr]$ rcsdiff -u -r1.19 -r1.20 avr.h|cat -vET
===================================================================
RCS file: avr.h,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- avr.h^I2001/02/05 04:11:54^I1.19$
+++ avr.h^I2001/04/16 18:30:36^I1.20$
@@ -2435,7 +2435,8 @@$
$
#define STRING_LIMIT^I((unsigned) 64)$
#define STRING_ASM_OP^I"\t.string\t"$
-/* Some svr4 assemblers have a limit on the number of
ch^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@of
a .string directive. If your assembler$
+/* Some svr4 assemblers have a limit on the number of characters which$
+ can appear in the operand of a .string directive. If your assembler$
has such a limitation, you should define STRING_LIMIT to reflect that$
limit. Note that at least some svr4 assemblers have a limit on the$
actual number of bytes in the double-quoted string, and that they$
@@ -3255,12 +3256,3 @@$
$
/* Get the standard ELF stabs definitions. */$
#include "dbxelf.h"$
-$
-#undef ASM_IDENTIFY_GCC$
-#define ASM_IDENTIFY_GCC(FILE)^I^I^I^I\$
-do^I^I^I^I^I^I^I\$
- {^I^I^I^I^I^I^I\$
- if (write_symbols != DBX_DEBUG)^I^I^I\$
- fputs ("gcc2_compiled.:\n", FILE);^I^I\$
- }^I^I^I^I^I^I^I\$
-while (0)$
>How-To-Repeat:
Examine the above diff. Compare with e.g. FTP snapshots for the
correct previous revision. Note that (at least) the diff between 1.19
and 1.19.2.1 has the same problem.
>Fix:
Fix the CVS file. Institute a system for storing and checking md5sums
for all previous revisions of all files in the CVS repository, to
detect corruption reliably.
>Release-Note:
>Audit-Trail:
>Unformatted: