This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: tests for compiler (non-)limits

On 01/05/2007, at 5:57 PM, Andrew Pinski wrote:

On 4/23/07, Geoffrey Keating <> wrote:
In 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
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.

Oops! I thought this was generating a 1M string literal, but it's actually generating a 100M string literal. I'll turn it down.

Any other problems?

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]