public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob dot quill at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/33962] ICE at call to overloaded template function with variable-length function argument list
Date: Fri, 16 Nov 2007 15:03:00 -0000	[thread overview]
Message-ID: <20071116150312.13935.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33962-8486@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from rob dot quill at gmail dot com  2007-11-16 15:03 -------
Hey,

I can confirm this and am trying to investigate the problem. It seems that
more_specialized_fn() loops over the arguments to the first overloaded
function, where in this case there are two, but the tree chain describing the
parameters for the function only contains 1 (i.e. it doesn't count the
ellipses). My current solution just changes the value of len to be at most the
number of items in the chain.

However, I suspect that there is actually something else wrong and that there
should be another node in the chain of type TYPE_PACK_EXPANSION which describes
the variadic-ness of the function.

If anyone can clarify this for me that would be much appreciated.

Rob Quill.


-- 


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


  reply	other threads:[~2007-11-16 15:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 19:20 [Bug c++/33962] New: " rjpeters at klab dot caltech dot edu
2007-11-16 15:03 ` rob dot quill at gmail dot com [this message]
2007-11-19  4:48 ` [Bug c++/33962] [4.1/4.2/4.3 Regression] " pinskia at gcc dot gnu dot org
2007-11-19 11:12 ` jakub at gcc dot gnu dot org
2007-11-20  6:26 ` jakub at gcc dot gnu dot org
2007-11-20  6:40 ` [Bug c++/33962] [4.1/4.2 " jakub at gcc dot gnu dot org
2008-02-01 17:02 ` jsm28 at gcc dot gnu dot org
2008-05-19 20:30 ` jsm28 at gcc dot gnu dot org
2008-07-04 22:53 ` [Bug c++/33962] [4.2 " jsm28 at gcc dot gnu dot org
2009-03-31  0:36 ` jsm28 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=20071116150312.13935.qmail@sourceware.org \
    --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).