This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: tests for compiler (non-)limits
- From: "Andrew Pinski" <pinskia at gmail dot com>
- To: "Geoffrey Keating" <gkeating at apple dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Tue, 1 May 2007 17:57:16 -0700
- Subject: Re: tests for compiler (non-)limits
- References: <20070424030219.043415E2537F@geoffk5.apple.com>
On 4/23/07, Geoffrey Keating <gkeating@apple.com> wrote:
In 5.4.2.1 in the C standard, there's a list of "translation limits".
The GNU coding standard says that a GNU program should "Avoid
arbitrary limits" and so does the C standard, and indeed GCC is
supposed to avoid most of these limits. (There are one or two limits
that are necessary to prevent run-away in the preprocessor.)
Some of these testcase fails if your /tmp only have 64Megs left.
/home/apinski/src/gcc-fsf/pointerplusexpr/gcc/gcc/testsuite/gcc.c-torture/compile/limits-stringlit.c:10:
fatal error: error writing to /tmp/ccPjWnUC.s: No space left on
device^M
compilation terminated.^M
FAIL: gcc.c-torture/compile/limits-stringlit.c -O0 (test for excess errors)
It seems wrong to require more 64 megs in /tmp. I have been running
the boostrap/testsuite without any problems til today.
Thanks,
Andrew Pinski