public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: a.metselaar@math.utwente.nl To: gcc-gnats@gcc.gnu.org Subject: libstdc++/5012: cannot instantiate std::binder1st<std::mem_fun1_t<void, unary_functor<const int&, void\>, const int&> > Date: Tue, 04 Dec 2001 11:46:00 -0000 [thread overview] Message-ID: <20011204194128.9223.qmail@sources.redhat.com> (raw) >Number: 5012 >Category: libstdc++ >Synopsis: cannot instantiate std::binder1st<std::mem_fun1_t<void, unary_functor<const int&, void\>, const int&> > >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Tue Dec 04 11:46:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Arnold Metselaar >Release: 3.0.2 (Debian) (Debian testing/unstable) >Organization: >Environment: System: Linux khumbu 2.2.19 #5 Thu Nov 22 20:52:49 CET 2001 i686 unknown Architecture: i686 host: i386-pc-linux-gnu build: i386-pc-linux-gnu target: i386-pc-linux-gnu configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,objc --prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --disable-checking --enable-threads=posix --enable-java-gc=boehm --with-cpp-install-dir=bin --enable-objc-gc i386-linux >Description: cannot instantiate std::binder1st<std::mem_fun1_t<void, unary_functor<const int&, void>, const int&> >; forming reference to reference transcript: arnold [~/test]$ g++-3.0 -Wall testbind.cpp /usr/include/g++-v3/bits/stl_function.h: In instantiation of `std::binder1st<std::mem_fun1_t<void, unary_functor<const int&, void>, const int&> >': testbind.cpp:22: instantiated from here /usr/include/g++-v3/bits/stl_function.h:228: forming reference to reference type `const int& const' /usr/include/g++-v3/bits/stl_function.h:234: forming reference to reference type `const int&' >How-To-Repeat: g++-3.0 -Wall testbind.cpp note: This problem is the same as #5011, but gccbug happily sent a bugreport without attachment >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="testbind.cpp"; name="testbind.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="testbind.cpp" dXNpbmcgbmFtZXNwYWNlIHN0ZDsKI2luY2x1ZGUgPGZ1bmN0aW9uYWw+Cgp0ZW1wbGF0ZSA8Y2xh c3MgQXJnLCBjbGFzcyBSZXM+IApzdHJ1Y3QgdW5hcnlfZnVuY3RvciA6IHB1YmxpYyB1bmFyeV9m dW5jdGlvbjxBcmcsUmVzPgp7CiAgdmlydHVhbCB+dW5hcnlfZnVuY3RvcigpIHt9CiAgdmlydHVh bCBSZXMgb3BlcmF0b3IoKSAoQXJnIHgpID0wOwogIGJpbmRlcjFzdDxtZW1fZnVuMV90PFJlcywg dW5hcnlfZnVuY3RvcjxBcmcsUmVzPiwgQXJnPiA+IAogIGZ1bmMoKQogIHsgcmV0dXJuIGJpbmQx c3QobWVtX2Z1bigmdW5hcnlfZnVuY3RvcjxBcmcsUmVzPjo6b3BlcmF0b3IoKSksdGhpcyk7IH0K fSA7CgpjbGFzcyBGIDogcHVibGljIHVuYXJ5X2Z1bmN0b3I8Y29uc3QgaW50ICYsdm9pZD4Kewog IHZvaWQgb3BlcmF0b3IoKSAoY29uc3QgaW50ICYgaSkgeyByZXR1cm47IH0KfSBmOwoKCmludCBt YWluKCkKewogIGYuZnVuYygpOwp9Cgo=
next reply other threads:[~2001-12-04 19:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-04 11:46 a.metselaar [this message] 2001-12-26 3:57 paolo 2002-01-21 20:57 rodrigc
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=20011204194128.9223.qmail@sources.redhat.com \ --to=a.metselaar@math.utwente.nl \ --cc=gcc-gnats@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: linkBe 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).