public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51878] ICE or OOM with decltype + variadic templates + "indirect" function call
Date: Tue, 17 Jan 2012 11:50:00 -0000	[thread overview]
Message-ID: <bug-51878-4-G7QolFUFrD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51878-4@http.gcc.gnu.org/bugzilla/>

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

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

--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-01-17 11:28:43 UTC ---
If I apply the below patchlet (parts of it are probably sane changes anyway) I
see a clean ICE with template instantiation depth exceeded. Then I wonder if
modulo the small tweaks we have just a duplicate of, eg, PR51304.

Maybe Jason can help triaging... (thanks in advance)

//////////////////

Index: error.c
===================================================================
--- error.c    (revision 183238)
+++ error.c    (working copy)
@@ -2471,6 +2471,10 @@ dump_expr (tree t, int flags)
       dump_expr (resolve_virtual_fun_from_obj_type_ref (t), flags);
       break;

+    case NONTYPE_ARGUMENT_PACK:
+      dump_template_argument (t, flags);
+      break;
+
       /*  This list is incomplete, but should suffice for now.
       It is very important that `sorry' does not call
       `report_error_function'.  That could cause an infinite loop.  */
Index: mangle.c
===================================================================
--- mangle.c    (revision 183238)
+++ mangle.c    (working copy)
@@ -2319,6 +2319,9 @@ write_bare_function_type (const tree type, const i
 {
   int java_method_p;

+  if (type == error_mark_node)
+    return;
+
   MANGLE_TRACE_TREE ("bare-function-type", type);

   /* Detect Java methods and emit special encoding.  */


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17  9:30 [Bug c++/51878] New: " b.r.longbons at gmail dot com
2012-01-17  9:53 ` [Bug c++/51878] " b.r.longbons at gmail dot com
2012-01-17 11:50 ` paolo.carlini at oracle dot com [this message]
2012-10-11 23:20 ` paolo.carlini at oracle dot com
2012-10-11 23:38 ` paolo at gcc dot gnu.org
2012-10-11 23:39 ` paolo.carlini at oracle dot com

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-51878-4-G7QolFUFrD@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).