public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, reichelt@igpm.rwth-aachen.de,
	rodrigc@gcc.gnu.org, serettov@hotmail.com
Subject: Re: c++/4897: ICE in gcc-3.0.2 during compilation of cyclone
Date: Wed, 14 Nov 2001 11:12:00 -0000	[thread overview]
Message-ID: <20011120033151.14349.qmail@sourceware.cygnus.com> (raw)

Synopsis: ICE in gcc-3.0.2 during compilation of cyclone

State-Changed-From-To: open->analyzed
State-Changed-By: rodrigc
State-Changed-When: Mon Nov 19 19:31:50 2001
State-Changed-Why:
    Confirmed with gcc 3.0.2 and gcc 3.0 branch.
    Note:
    The problem does not occur if compiled with the C++ compiler.
    
    Also, under gcc 3.1, this problem does not seem to occur.
    
    If I run cc1plus under a debugger, the stack trace I get is:
    
    0x080c3a80 in host_integerp (t=0x0, pos=0) at tree.c:3440
    3440      return (TREE_CODE (t) == INTEGER_CST
    (gdb) where
    #0  0x080c3a80 in host_integerp (t=0x0, pos=0) at tree.c:3440
    #1  0x08127a5e in store_constructor (exp=0x40192440,
        target=0x4019e840, align=32, cleared=0, size=0) at expr.c:4578
    #2  0x081310a2 in expand_expr (exp=0x40192440, target=0x4019e840,
        tmode=BLKmode, modifier=EXPAND_NORMAL) at expr.c:6629
    #3  0x08125eee in store_expr (exp=0x40192440, target=0x4019e840,
        want_value=0) at expr.c:4042
    #4  0x08125692 in expand_assignment (to=0x4019aaf8, from=0x40192440,
        want_value=0, suggest_reg=0) at expr.c:3866
    #5  0x0811367b in expand_decl_init (decl=0x4019aaf8) at stmt.c:3987
    #6  0x08099bca in emit_local_var (decl=0x4019aaf8)
        at c-semantics.c:337
    #7  0x08099e1f in genrtl_decl_stmt (t=0x4018fb90)
        at c-semantics.c:419
    #8  0x0809b92c in expand_stmt (t=0x4018fb90) at c-semantics.c:820
    #9  0x0809b63c in genrtl_compound_stmt (t=0x4018fa28)
        at c-semantics.c:739
    #10 0x0809b98b in expand_stmt (t=0x4018fa28) at c-semantics.c:840
    #11 0x0806caa9 in c_expand_body (fndecl=0x4019a4e0, nested_p=0)
        at c-decl.c:6758
    #12 0x0806c818 in finish_function (nested=0) at c-decl.c:6697
    #13 0x0804a63a in yyparse_1 () at /usr/lib/bison.simple:324
    #14 0x08051c15 in yyparse () at c-lex.c:158
    #15 0x080b1ea9 in compile_file (name=0x844ae9a "b.c")
        at toplev.c:2369
    #16 0x080b6c9b in main (argc=2, argv=0xbffff774) at toplev.c:4990
    #17 0x400402ae in __libc_start_main (main=0x80b63fe <main>, argc=2,
        ubp_av=0xbffff774, init=0x80491b8 <_init>,

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4897&database=gcc


             reply	other threads:[~2001-11-20  3:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 11:12 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-07 15:26 rodrigc
2001-12-07 15:20 rodrigc
2001-11-14 11:14 rodrigc
2001-11-13  9:26 serettov

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=20011120033151.14349.qmail@sourceware.cygnus.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=reichelt@igpm.rwth-aachen.de \
    --cc=serettov@hotmail.com \
    /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).