public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51344] cc1plus hangs when compiling
Date: Tue, 17 Jan 2012 11:24:00 -0000	[thread overview]
Message-ID: <bug-51344-4-4t4AB3NqxI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51344-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51344

Kai Tietz <ktietz at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ktietz at gcc dot gnu.org

--- Comment #4 from Kai Tietz <ktietz at gcc dot gnu.org> 2012-01-17 11:09:13 UTC ---
I investigated a bit and the cause for the endless loop is, that the
attribute-list for this decl is pointing to itself.  So in loops for ever in
private_lookup_attribute.

I get following backtrace in gdb for it

#0  0x0068853f in private_lookup_attribute (attr_name=0x100e1c8 "gnu_inline",
    attr_len=10, list=0x7ee3ce58) at ../../gcc/gcc/tree.c:5254
#1  0x00446308 in start_preparsed_function (decl1=0x7ee71880, attrs=0x0,
    flags=3) at ../../gcc/gcc/tree.h:4592
#2  0x0051d4b8 in cp_parser_type_specifier (parser=0x7ee80ce8,
    flags=<value optimized out>, decl_specs=0x5a4ca8c,
    is_declaration=1 '\001', declares_class_or_enum=0x5a4ca44,
    is_cv_qualifier=0x5a4ca4b "") at ../../gcc/gcc/cp/parser.c:21675
#3  0x00530f82 in cp_parser_decl_specifier_seq (parser=0x7ee80ce8, flags=1,
    decl_specs=0x5a4ca8c, declares_class_or_enum=0x5a4cae4)
    at ../../gcc/gcc/cp/parser.c:10696
#4  0x00537588 in cp_parser_single_declaration (parser=0x7ee80ce8,
    checks=0x0, member_p=0 '\0', explicit_specialization_p=0 '\0',
    friend_p=0x5a4cb4b "") at ../../gcc/gcc/cp/parser.c:21271
#5  0x00537a23 in cp_parser_template_declaration_after_export (
    parser=0x7ee80ce8, member_p=30 '\036') at ../../gcc/gcc/cp/parser.c:21157
#6  0x00541749 in cp_parser_declaration (parser=0x7ee80ce8)
    at ../../gcc/gcc/cp/parser.c:10160


  parent reply	other threads:[~2012-01-17 11:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 14:06 [Bug c++/51344] New: " koliasvskj at gmail dot com
2011-11-29 14:33 ` [Bug c++/51344] " keithmarshall at mailinator dot com
2011-12-02 16:10 ` paolo.carlini at oracle dot com
2011-12-02 18:58 ` koliasvskj at gmail dot com
2012-01-17 11:24 ` ktietz at gcc dot gnu.org [this message]
2012-01-18 20:27 ` [Bug c++/51344] [4.4/4.5/4.6/4.7 regression] " jason at gcc dot gnu.org
2012-01-19 13:56 ` rguenth at gcc dot gnu.org
2012-01-19 22:29 ` ktietz at gcc dot gnu.org
2012-01-19 23:04 ` ktietz at gcc dot gnu.org
2012-01-19 23:09 ` ktietz at gcc dot gnu.org
2012-01-19 23:13 ` ktietz at gcc dot gnu.org
2012-01-19 23:16 ` ktietz at gcc dot gnu.org
2021-04-29 18:42 ` cvs-commit at gcc dot gnu.org
2022-01-27 21:55 ` cvs-commit at gcc dot gnu.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=bug-51344-4-4t4AB3NqxI@http.gcc.gnu.org/bugzilla/ \
    --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).