public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com
To: gcc-gnats@gcc.gnu.org
Cc: dj@redhat.com
Subject: c/4388: Failure of gcc.c-torture/execute/20010924-1.c on irix6.5
Date: Mon, 24 Sep 2001 21:36:00 -0000	[thread overview]
Message-ID: <20010925042958.28158.qmail@sourceware.cygnus.com> (raw)

>Number:         4388
>Category:       c
>Synopsis:       Failure of gcc.c-torture/execute/20010924-1.c on irix6.5
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Sep 24 21:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     David Billinghurst
>Release:        GNU C version 3.1 20010924 (experimental) (mips-sgi-irix6.5)
>Organization:
>Environment:
mips-sgi-irix6.5
>Description:
New test gcc.c-torture/execute/20010924-1.c fails on irix6.5.

The error is:

/exd4/billingd/src/gcc-mainline/gcc/testsuite/gcc.c-torture/execute/20010924-1.c:28: Internal error: Segmentation fault

Running under gdb I see:

Starting program: /exd4/billingd/obj/gcc-mainline/gcc/cc1 -fpreprocessed 20010924-1.i -quiet -dumpbase 20010924-1.c -O0 -w -version -o 20010924-1.s
GNU CPP version 3.1 20010924 (experimental) (cpplib) [AL 1.1, MM 40] SGI running IRIX 6.x
GNU C version 3.1 20010924 (experimental) (mips-sgi-irix6.5)
        compiled by GNU C version 3.1 20010924 (experimental).

Program received signal SIGSEGV, Segmentation fault.
0x100619c4 in digest_init (type=0x10450f00, init=0x74, require_constant=1, 
    constructor_constant=1)
    at /exd4/billingd/src/gcc-mainline/gcc/c-typeck.c:4693
4693                  && TREE_CODE (TYPE_SIZE (type)) == INTEGER_CST
(gdb) where
#0  0x100619c4 in digest_init (type=0x10450f00, init=0x74, require_constant=1, 
    constructor_constant=1)
    at /exd4/billingd/src/gcc-mainline/gcc/c-typeck.c:4693
#1  0x10065100 in output_init_element (value=0x10440240, type=0x10450f00, 
    field=0x10450f78, pending=1)
    at /exd4/billingd/src/gcc-mainline/gcc/c-typeck.c:6255
#2  0x10065ce0 in process_init_element (value=0x10440240)
    at /exd4/billingd/src/gcc-mainline/gcc/c-typeck.c:6533
#3  0x1002c6e4 in yyparse_1 () at bison.simple:1437
#4  0x10034904 in yyparse () at /exd4/billingd/src/gcc-mainline/gcc/c-lex.c:166
#5  0x100c3e54 in compile_file (name=0x10420f30 "20010924-1.i")
    at /exd4/billingd/src/gcc-mainline/gcc/toplev.c:2328
#6  0x100c9b7c in toplev_main (argc=11, argv=0x7ffedf04)
    at /exd4/billingd/src/gcc-mainline/gcc/toplev.c:4973
#7  0x10099f9c in main (argc=11, argv=0x1043c1e0)
    at /exd4/billingd/src/gcc-mainline/gcc/main.c:34

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-09-24 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24 21:36 David.Billinghurst [this message]
2001-12-09 18:47 billingd
2001-12-09 18:56 billingd

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=20010925042958.28158.qmail@sourceware.cygnus.com \
    --to=david.billinghurst@riotinto.com \
    --cc=dj@redhat.com \
    --cc=gcc-gnats@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).