public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/4794 Date: Wed, 01 Jan 2003 19:36:00 -0000 [thread overview] Message-ID: <20030101193600.3009.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/4794; it has been noted by GNATS. From: Nathanael Nerode <neroden@twcny.rr.com> To: fritz@intrinsity.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/4794 Date: Wed, 1 Jan 2003 14:32:41 -0500 This is confirmed still present in mainline as of 2003-01-01. There seems to be an infinite recursion in constant folding -- hope this helps somebody track it down. GDB backtrace shows: #1 0x08309478 in has_cleanups (exp=0x401811e0) at ../../gcc/gcc/tree.c:1820 #2 0x08309478 in has_cleanups (exp=0x40181420) at ../../gcc/gcc/tree.c:1820 #3 0x08309478 in has_cleanups (exp=0x40180208) at ../../gcc/gcc/tree.c:1820 ...etc for a long time... This is the top of the backtrace: #95 0x081d23a3 in fold (expr=0x40180a64) at ../../gcc/gcc/fold-const.c:7231 #96 0x080ea175 in condition_conversion (expr=0x40185d60) at ../../gcc/gcc/cp/typeck.c:3919 #97 0x08106620 in maybe_convert_cond (cond=0x40185d60) at ../../gcc/gcc/cp/semantics.c:200 #98 0x08106722 in finish_if_stmt_cond (cond=0x40185d60, if_stmt=0x40147be0) at ../../gcc/gcc/cp/semantics.c:261 #99 0x080d3df9 in cp_parser_selection_statement (parser=0x40177bd0) at ../../gcc/gcc/cp/parser.c:6026 #100 0x080d3a39 in cp_parser_statement (parser=0x40177bd0) at ../../gcc/gcc/cp/parser.c:5761 #101 0x080d3d21 in cp_parser_statement_seq_opt (parser=0x40177bd0) at ../../gcc/gcc/cp/parser.c:5969 #102 0x080d3cd7 in cp_parser_compound_statement (parser=0x40177bd0) at ../../gcc/gcc/cp/parser.c:5941 #103 0x080d81ed in cp_parser_function_body (parser=0x40177bd0) at ../../gcc/gcc/cp/parser.c:11162 #104 0x080d8217 in cp_parser_ctor_initializer_opt_and_function_body ( parser=0x40177bd0) at ../../gcc/gcc/cp/parser.c:11179 #105 0x080db449 in cp_parser_function_definition_after_declarator ( parser=0x40177bd0, inline_p=false) at ../../gcc/gcc/cp/parser.c:14055 #106 0x080db39b in cp_parser_function_definition_from_specifiers_and_declarator (parser=0x40177bd0, decl_specifiers=0x40167dfc, attributes=0x0, declarator=0x40147ba0, access_checks=0x0) at ../../gcc/gcc/cp/parser.c:13998 #107 0x080d6d91 in cp_parser_init_declarator (parser=0x40177bd0, decl_specifiers=0x40167dfc, prefix_attributes=0x0, access_checks=0x0, function_definition_allowed_p=true, member_p=false, function_definition_p=0xbffff9e0) at ../../gcc/gcc/cp/parser.c:9747 #108 0x080d4743 in cp_parser_simple_declaration (parser=0x40177bd0, function_definition_allowed_p=true) at ../../gcc/gcc/cp/parser.c:6731 #109 0x080d46d4 in cp_parser_block_declaration (parser=0x40177bd0, statement_p=false) at ../../gcc/gcc/cp/parser.c:6671 #110 0x080d45ce in cp_parser_declaration (parser=0x40177bd0) at ../../gcc/gcc/cp/parser.c:6591 #111 0x080d4474 in cp_parser_declaration_seq_opt (parser=0x40177bd0) at ../../gcc/gcc/cp/parser.c:6516 #112 0x080d0b29 in cp_parser_translation_unit (parser=0x40177bd0) at ../../gcc/gcc/cp/parser.c:2530 #113 0x080dc301 in yyparse () at ../../gcc/gcc/cp/parser.c:14901 #114 0x0813540d in c_common_parse_file (set_yydebug=0) at ../../gcc/gcc/c-lex.c:161 #115 0x082fff76 in compile_file () at ../../gcc/gcc/toplev.c:2128 #116 0x08304ea6 in do_compile () at ../../gcc/gcc/toplev.c:5352 #117 0x08304eff in toplev_main (argc=2, argv=0xbffffc14) at ../../gcc/gcc/toplev.c:5382 #118 0x0814b330 in main (argc=2, argv=0xbffffc14) at ../../gcc/gcc/main.c:37
reply other threads:[~2003-01-01 19:36 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=20030101193600.3009.qmail@sources.redhat.com \ --to=neroden@twcny.rr.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).