public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "a71104 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/47212] New: [C++0x] crash on lambda returning lambda
Date: Fri, 07 Jan 2011 15:00:00 -0000	[thread overview]
Message-ID: <bug-47212-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [C++0x] crash on lambda returning lambda
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: a71104@gmail.com


Here's the code:



==============================================

#include <iostream>
using namespace std;

auto test = [] () {
    return [] (istream &ris) -> istream& {
        return ris;
    };
};

int main() {
    cin >> test();
    return 0;
}

==============================================



I'm not sure whether this code is correct but it just crashes g++ 4.5.0.
I'm compiling with:

g++ -std=c++0x -pedantic -Wall Test.cpp



I'm doing code like that because I wish to implement a custom parameterized I/O
manipulator without using implementation-specific types such as smanip and
stuff.
Note that it doesn't crash if I just call test() without using the result on
cin, thus I think the problem is matching the returned lambda against the
version of operator >> that takes a function as an argument.

PS: I don't think there's any difference but I'm using MinGW and I'm currently
unable to test on Linux with real g++.


             reply	other threads:[~2011-01-07 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 15:00 a71104 at gmail dot com [this message]
2011-01-07 15:28 ` [Bug c++/47212] " redi at gcc dot gnu.org
2011-05-27 17:28 ` 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-47212-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).