public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/18852] New: [3.4 Regression] 8 tests fail: SIGSEGV for stack growth failure
Date: Sun, 05 Dec 2004 21:38:00 -0000 [thread overview]
Message-ID: <20041205213837.18852.danglin@gcc.gnu.org> (raw)
We have the following new fails in the C testsuite:
Running /xxx/gnu/gcc-3.4/gcc/gcc/testsuite/gcc.dg/compat/compat.exp ...
FAIL: gcc.dg/compat/scalar-by-value-4 c_compat_x_tst.o compile
FAIL: gcc.dg/compat/scalar-by-value-4 c_compat_y_tst.o compile
FAIL: gcc.dg/compat/scalar-return-4 c_compat_x_tst.o compile
FAIL: gcc.dg/compat/scalar-return-4 c_compat_y_tst.o compile
FAIL: gcc.dg/compat/struct-by-value-11 c_compat_x_tst.o compile
FAIL: gcc.dg/compat/struct-by-value-11 c_compat_y_tst.o compile
FAIL: gcc.dg/compat/struct-by-value-12 c_compat_x_tst.o compile
FAIL: gcc.dg/compat/struct-by-value-12 c_compat_y_tst.o compile
All these fail due SIGSEGVs:
Executing on host: /xxx/gnu/gcc-3.4/objdir/gcc/xgcc -B/xxx/gnu/gcc-3.4/objdir/gc
c/ -c -o c_compat_x_tst.o /xxx/gnu/gcc-3.4/gcc/gcc/testsuite/gcc.dg/compat/s
calar-by-value-4_x.c (timeout = 300)
^M
Pid 21061 received a SIGSEGV for stack growth failure.^M
Possible causes: insufficient memory or swap space,^M
or stack size exceeded maxssiz.^M
xgcc: Internal error: Segmentation fault (program cc1)
Please submit a full bug report.
--
Summary: [3.4 Regression] 8 tests fail: SIGSEGV for stack growth
failure
Product: gcc
Version: 3.4.4
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: danglin at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: hppa2.0w-hp-hpux11.00
GCC host triplet: hppa2.0w-hp-hpux11.00
GCC target triplet: hppa2.0w-hp-hpux11.00
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18852
next reply other threads:[~2004-12-05 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 21:38 danglin at gcc dot gnu dot org [this message]
2004-12-05 21:43 ` [Bug middle-end/18852] " pinskia at gcc dot gnu dot org
2004-12-05 21:43 ` ebotcazou at gcc dot gnu dot org
2004-12-05 21:55 ` dave at hiauly1 dot hia dot nrc dot ca
2004-12-06 16:54 ` ebotcazou at gcc dot gnu dot org
2004-12-06 17:52 ` dave at hiauly1 dot hia dot nrc dot ca
2004-12-06 18:34 ` giovannibajo at libero dot it
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=20041205213837.18852.danglin@gcc.gnu.org \
--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).