public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: gcc-gnats@gcc.gnu.org
Subject: c/7068: ICE with incomplete types
Date: Tue, 18 Jun 2002 09:16:00 -0000	[thread overview]
Message-ID: <200206181550.RAA365958@bartok.TechFak.Uni-Bielefeld.DE> (raw)


>Number:         7068
>Category:       c
>Synopsis:       ICE with incomplete types
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-illegal-code
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 18 08:56:11 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Rainer Orth
>Release:        3.2 20020617 (experimental)
>Organization:
Faculty of Technology, Bielefeld University
>Environment:
System: OSF1 bartok V5.1 732 alpha
Machine: alpha
	
host: alpha-dec-osf5.1
build: alpha-dec-osf5.1
target: alpha-dec-osf5.1
configured with: /vol/gnu/src/gcc/gcc/configure --prefix=/vol/gcc --with-local-prefix=/vol/gcc --disable-nls alpha-dec-osf5.1
>Description:
During a bootstrap, cc1 crashed on the equivalent of the following code:

struct itimerspec {
        struct timespec it_interval;
        struct timespec it_value;
};

% ./xgcc -B./ -g -v crash.i 
Reading specs from ./specs
Configured with: /vol/gnu/src/gcc/gcc/configure --prefix=/vol/gcc --with-local-prefix=/vol/gcc --disable-nls alpha-dec-osf5.1
Thread model: single
gcc version 3.2 20020617 (experimental)
 ./cc1 -fpreprocessed crash.i -quiet -dumpbase crash.i -g -version -o /tmp//ccOO1w7z.s
GNU C version 3.2 20020617 (experimental) (alpha-dec-osf5.1)
        compiled by GNU C version 3.1.
crash.i:2: error: field `it_interval' has incomplete type
crash.i:3: error: field `it_value' has incomplete type
crash.i:4: internal compiler error: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

The problem only happens with -g.  gcc 3.1 is ok as well, so this is a
regression.
	
>How-To-Repeat:
Compile the code above.
	
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-06-18 15:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200206181550.RAA365958@bartok.TechFak.Uni-Bielefeld.DE \
    --to=ro@techfak.uni-bielefeld.de \
    --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).