public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/20225] New: [4.0/4.1 regression] ICE during GC
Date: Sun, 27 Feb 2005 10:47:00 -0000 [thread overview]
Message-ID: <20050226232106.20225.schwab@suse.de> (raw)
$ ./cc1plus -fpreprocessed libkspreadpart_la.all_cc.ii -quiet -O -w
Program received signal SIGSEGV, Segmentation fault.
gt_ggc_mx_cgraph_node (x_p=<value optimized out>) at gtype-desc.c:188
188 gt_ggc_m_9tree_node ((*x).decl);
(gdb) bt
#0 gt_ggc_mx_cgraph_node (x_p=<value optimized out>) at gtype-desc.c:188
#1 0x40000000004a3a80 in gt_ggc_mx_cgraph_node (x_p=<value optimized out>)
at gtype-desc.c:196
#2 0x40000000004a3a80 in gt_ggc_mx_cgraph_node (x_p=<value optimized out>)
at gtype-desc.c:196
#3 0x40000000004ab120 in gt_ggc_m_P11cgraph_node4htab (
x_p=<value optimized out>) at gtype-desc.c:1498
#4 0x400000000049eff0 in ggc_mark_roots () at ggc-common.c:118
#5 0x4000000000662110 in ggc_collect () at ggc-page.c:1981
#6 0x400000000066c690 in rest_of_compilation () at passes.c:477
#7 0x4000000000204e40 in execute_pass_list (pass=0x6000000000016e90)
at tree-optimize.c:533
#8 0x4000000000205600 in tree_rest_of_compilation (fndecl=0x200000000af51fb0)
at tree-optimize.c:669
#9 0x4000000000131630 in expand_body (fn=0x200000000af51fb0)
at semantics.c:2977
#10 0x40000000006a0f30 in cgraph_expand_function (node=0x2000000010652e50)
at cgraphunit.c:832
#11 0x40000000006a3d30 in cgraph_optimize () at cgraphunit.c:1699
#12 0x40000000000afd10 in cp_finish_file () at decl2.c:3032
#13 0x4000000000003630 in finish_file () at cp-lang.c:113
#14 0x40000000001c58a0 in c_common_parse_file (
set_yydebug=<value optimized out>) at c-opts.c:1096
#15 0x4000000000624380 in toplev_main (argc=<value optimized out>,
argv=<value optimized out>) at toplev.c:996
#16 0x40000000001d8380 in main (argc=6, argv=0x60000fffffffa858) at main.c:35
(gdb) p x
$1 = (struct cgraph_node *) 0x0
--
Summary: [4.0/4.1 regression] ICE during GC
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: schwab at suse dot de
CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: ia64-suse-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20225
next reply other threads:[~2005-02-26 23:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 10:47 schwab at suse dot de [this message]
2005-02-27 11:16 ` [Bug c++/20225] " schwab at suse dot de
2005-02-27 11:25 ` [Bug middle-end/20225] " pinskia at gcc dot gnu dot org
2005-02-27 12:53 ` pinskia at gcc dot gnu dot org
2005-02-27 13:54 ` pinskia at gcc dot gnu dot org
2005-02-27 21:37 ` schwab at suse dot de
2005-02-27 22:05 ` schwab at suse dot de
2005-03-03 12:56 ` schwab at suse dot de
2005-03-04 18:09 ` rth at gcc dot gnu dot org
2005-03-10 13:37 ` rth at gcc dot gnu dot org
2005-03-10 15:15 ` rth at gcc dot gnu dot org
2005-03-13 5:20 ` pinskia at gcc dot gnu dot org
2005-03-18 14:57 ` cvs-commit at gcc dot gnu dot org
2005-03-18 18:16 ` cvs-commit at gcc dot gnu dot org
2005-03-24 17:44 ` mmitchel at gcc dot gnu dot org
2005-03-25 11:05 ` jakub at gcc dot gnu dot org
2005-03-27 19:35 ` hubicka at gcc dot gnu dot org
2005-04-01 13:11 ` pinskia at gcc dot gnu dot org
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=20050226232106.20225.schwab@suse.de \
--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).