public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "piotr dot wyderski at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/42447]  New: ICE during processing complex templates
Date: Mon, 21 Dec 2009 12:38:00 -0000	[thread overview]
Message-ID: <bug-42447-17090@http.gcc.gnu.org/bugzilla/> (raw)

Compile the attached sources as follows:

 g++ -std=gnu++0x -c -Wno-pmf-conversions file_reader.cpp

An Internal Compiler Error report will appear:

file_reader.cpp: In instantiation of
'std::unique_ptr<base::dynamic_dispatch<void
(io::file_reader::*)(io::request&)>::entry [], base::release_deleter>':
file_reader.cpp:35664:39:   instantiated from 'std::unique_ptr<_Tp [],
_Tp_Deleter>::unique_ptr() [with _Tp = base::dynamic_dispatch<void
(io::file_reader::*)(io::request&)>::entry, _Tp_Deleter =
base::release_deleter]'
file_reader.cpp:86579:76:   instantiated from 'base::dynamic_dispatch<TR
(TC::*)(TD&, TA ...)>::dynamic_dispatch(TR (TC::*)(TD&, TA ...), size_t) [with
TC = io::file_reader, TR = void, TD = io::request, TA = {}, TR (TC::*)(TD&, TA
...) = void (io::file_reader::*)(io::request&), size_t = unsigned int]'
file_reader.cpp:88954:55:   instantiated from here
file_reader.cpp:35653:5: internal compiler error: in finish_member_declaration,
at cp/semantics.c:2445
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


-- 
           Summary: ICE during processing complex templates
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: piotr dot wyderski at gmail dot com
  GCC host triplet: Cygwin/GCC-trunk


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


             reply	other threads:[~2009-12-21 12:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 12:38 piotr dot wyderski at gmail dot com [this message]
2009-12-21 12:41 ` [Bug c++/42447] " piotr dot wyderski at gmail dot com
2009-12-21 13:00 ` paolo dot carlini at oracle dot com
2009-12-21 13:47 ` [Bug c++/42447] [C++0x] " piotr dot wyderski at gmail dot com
2009-12-21 14:11 ` paolo dot carlini at oracle dot com
2009-12-21 14:28 ` piotr dot wyderski at gmail dot com
2009-12-21 14:34 ` paolo dot carlini at oracle dot com
2009-12-21 16:09 ` pinskia at gcc dot gnu dot org
2009-12-21 16:14 ` paolo dot carlini at oracle dot com
2009-12-21 16:38 ` piotr dot wyderski at gmail dot com
2009-12-21 16:49 ` paolo dot carlini at oracle dot com
2009-12-21 17:18 ` paolo dot carlini at oracle dot com
2009-12-21 17:24 ` piotr dot wyderski at gmail dot com
2009-12-21 17:31 ` paolo dot carlini at oracle dot com
2009-12-21 17:39 ` piotr dot wyderski at gmail dot com
2009-12-21 18:33 ` [Bug c++/42447] [4.5 Regresson] " paolo dot carlini at oracle dot com
2009-12-21 20:29 ` paolo dot carlini at oracle dot com
2009-12-21 20:54 ` hjl dot tools at gmail dot com
2009-12-28 19:53 ` [Bug c++/42447] [4.5 Regression] " jason at gcc dot gnu dot org
2009-12-29  3:33 ` jason at gcc dot gnu dot org
2009-12-30 19:36 ` jason at gcc dot gnu dot org
2010-01-07 22:24 ` hjl 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=bug-42447-17090@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).