This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] New c-torture testcases.
- To: dnovillo at redhat dot com
- Subject: Re: [patch] New c-torture testcases.
- From: Jeffrey Oldham <oldham at codesourcery dot com>
- Date: Sat, 26 May 2001 15:14:46 -0700
- cc: oldham at codesourcery dot com, gcc-patches at gcc dot gnu dot org
- Reply-to: oldham at codesourcery dot com
Index: gcc.c-torture/compile/20010518-2.c
===================================================================
+ /* Large static storage. */
+
+ static volatile char chars_1[INT_MAX / 2];
INT_MAX/2 = 2^{31} seems excessive. MIPS's assembler complains about
allocating such a large number:
spawn /am/mother/vol/vol2/frameworks/pooma/joldham/dev4/gcc/objdir/gcc/xgcc -B/am/mother/vol/vol2/frameworks/pooma/joldham/dev4/gcc/objdir/gcc/ /users/joldham/pooma/dev4/gcc/gcc/testsuite/gcc.c-torture/compile/20010518-2.c -w -O0 -c -o /users/joldham/pooma/dev4/gcc/objdir/gcc/testsuite/20010518-2.o
as: Error: /var/tmp//cctxXzfv.s, line 68: Not enough space
as: Error: /var/tmp//cctxXzfv.s, line 68: could not allocate enough memory for .space
compiler exited with status 1
output is:
as: Error: /var/tmp//cctxXzfv.s, line 68: Not enough space
as: Error: /var/tmp//cctxXzfv.s, line 68: could not allocate enough memory for .space
What is the test's purpose? Can we find a different way to test the
same thing that does not cause problems for assemblers?
Thanks,
Jeffrey D. Oldham
oldham@codesourcery.com