public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "darpeer at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59271] New: a.C:16:21: internal compiler error: in strip_typedefs, at cp/tree.c:1315
Date: Sun, 24 Nov 2013 03:36:00 -0000	[thread overview]
Message-ID: <bug-59271-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 59271
           Summary: a.C:16:21: internal compiler error: in strip_typedefs,
                    at cp/tree.c:1315
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: darpeer at hotmail dot com

void f(int n)
{
  int  a[n];

  for (auto& i : a)
    {
      i = &i - a;
    }

  [&a] (auto m)
    {
      for (auto i : a)
    {
      cout << i << endl;
    }

      return m;
    };
}

g++ -std=c++1y -ggdb3 -o a a.C
a.C: In lambda function:
a.C:16:21: internal compiler error: in strip_typedefs, at cp/tree.c:1315
       for (auto i : a)
                     ^
0x74b642 strip_typedefs(tree_node*)
    ../../trunk/gcc/cp/tree.c:1315
0x74b221 strip_typedefs(tree_node*)
    ../../trunk/gcc/cp/tree.c:1190
0x5e1b22 canonicalize_type_argument
    ../../trunk/gcc/cp/pt.c:6231
0x6278f9 unify
    ../../trunk/gcc/cp/pt.c:17445
0x6301f8 unify_one_argument
    ../../trunk/gcc/cp/pt.c:16116
0x624fe9 type_unification_real
    ../../trunk/gcc/cp/pt.c:16188
0x638d02 do_auto_deduction(tree_node*, tree_node*, tree_node*)
    ../../trunk/gcc/cp/pt.c:21418
0x68e4b3 build_range_temp
    ../../trunk/gcc/cp/parser.c:10068
0x6c1ddb do_range_for_auto_deduction
    ../../trunk/gcc/cp/parser.c:10091
0x6c1ddb cp_parser_range_for
    ../../trunk/gcc/cp/parser.c:10046
0x6c1ddb cp_parser_for
    ../../trunk/gcc/cp/parser.c:9970
0x6c1ddb cp_parser_iteration_statement
    ../../trunk/gcc/cp/parser.c:10436
0x6a0259 cp_parser_statement
    ../../trunk/gcc/cp/parser.c:9297
0x6a1419 cp_parser_statement_seq_opt
    ../../trunk/gcc/cp/parser.c:9674
0x6a2b18 cp_parser_lambda_body
    ../../trunk/gcc/cp/parser.c:9178
0x6a2b18 cp_parser_lambda_expression
    ../../trunk/gcc/cp/parser.c:8693
0x6a2b18 cp_parser_primary_expression
    ../../trunk/gcc/cp/parser.c:4309
0x6a49e9 cp_parser_postfix_expression
    ../../trunk/gcc/cp/parser.c:5908
0x6a71c8 cp_parser_unary_expression
    ../../trunk/gcc/cp/parser.c:7109
0x6a7e5f cp_parser_binary_expression
    ../../trunk/gcc/cp/parser.c:7813
Please submit a full bug report,
with preprocessed source if appropriate.


             reply	other threads:[~2013-11-24  3:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24  3:36 darpeer at hotmail dot com [this message]
2013-11-24  3:38 ` [Bug c++/59271] " darpeer at hotmail dot com
2013-11-24 12:21 ` [Bug c++/59271] [4.9 Regression] " mpolacek at gcc dot gnu.org
2013-11-25  9:16 ` rguenth at gcc dot gnu.org
2013-11-28 12:07 ` jakub at gcc dot gnu.org
2013-12-24  4:22 ` jason at gcc dot gnu.org
2013-12-27 21:53 ` jason 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-59271-4@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).