public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/38605]  New: Out of stack space on gcc.c-torture/compile/limits-exprparen.c
Date: Mon, 22 Dec 2008 14:47:00 -0000	[thread overview]
Message-ID: <bug-38605-11113@http.gcc.gnu.org/bugzilla/> (raw)

Since at least r138218, the regress test for powerpc-apple-darwin8.5.0 has been
showing the new failures of...

FAIL: gcc.c-torture/compile/limits-exprparen.c  -O0  (test for excess errors)
FAIL: gcc.c-torture/compile/limits-exprparen.c  -O1  (test for excess errors)
FAIL: gcc.c-torture/compile/limits-exprparen.c  -O2  (test for excess errors)
FAIL: gcc.c-torture/compile/limits-exprparen.c  -O3 -fomit-frame-pointer  (test
for excess errors)
FAIL: gcc.c-torture/compile/limits-exprparen.c  -O3 -g  (test for excess
errors)
FAIL: gcc.c-torture/compile/limits-exprparen.c  -Os  (test for excess error

The last build without these failures was r138218 but there was a large gap in
builds during the tuples merge. The failures are logged as...

Executing on host: /Users/regress/tbox/native/build/gcc/xgcc
-B/Users/regress/tbox/native/build/gcc/   -O0  -w -c  -o limits-exprparen.o
/Users/regress/tbox/svn-gcc/gcc/testsuite/gcc.c-torture/compile/limits-exprparen.c
   (timeout = 300)
Out of stack space.
Try running 'ulimit -S -s unlimited' in the shell to raise its limit.
compiler exited with status 1
output is:
Out of stack space.
Try running 'ulimit -S -s unlimited' in the shell to raise its limit.

FAIL: gcc.c-torture/compile/limits-exprparen.c  -O0  (test for excess errors)

Geoff Keating suggests this indicates the test is no longer testing if the
stack space for gcc is reasonable. I don't see this on a dual G5 with 4GB of
ram running darwin9 but regress is a G4 with less ram (I assume) running
darwin8.


-- 
           Summary: Out of stack space on gcc.c-torture/compile/limits-
                    exprparen.c
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: howarth at nitro dot med dot uc dot edu
 GCC build triplet: powerpc-apple-darwin8.5.0
  GCC host triplet: powerpc-apple-darwin8.5.0
GCC target triplet: powerpc-apple-darwin8.5.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38605


             reply	other threads:[~2008-12-22 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22 14:47 howarth at nitro dot med dot uc dot edu [this message]
2008-12-22 14:50 ` [Bug testsuite/38605] " howarth at nitro dot med dot uc dot edu
2008-12-29  7:26 ` pinskia at gcc dot gnu dot org
2010-08-19 11:35 ` raju dot goruganti at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-38605-11113@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).