public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: levon@movementarian.org To: gcc-gnats@gcc.gnu.org Subject: c++/9486: boost_no_mem_tem_keyword fails with no matching function Date: Tue, 28 Jan 2003 19:26:00 -0000 [thread overview] Message-ID: <20030128191654.3729.qmail@sources.redhat.com> (raw) >Number: 9486 >Category: c++ >Synopsis: boost_no_mem_tem_keyword fails with no matching function >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Tue Jan 28 19:26:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: levon@movementarian.org >Release: current CVS HEAD >Organization: >Environment: Linux >Description: The below testcase (from boost configure tests) fails with : b.c: In function `void test_proc(T) [with T = int]': b.c:33: instantiated from here b.c:25: error: no matching function for call to `foo<double>::mfoo(int&)' >How-To-Repeat: g++ b.c >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="b.c" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="b.c" dGVtcGxhdGUgPGNsYXNzIFQ+CnN0cnVjdCBmb28KewogICB0ZW1wbGF0ZSA8Y2xhc3MgVT4KICAg c3RydWN0IG5lc3RlZAogICB7CiAgICAgIHR5cGVkZWYgZm9vPFU+IG90aGVyOwogICB9OwogICB0 ZW1wbGF0ZSA8Y2xhc3MgVT4KICAgdm9pZCBtZm9vKGNvbnN0IFUmKTsKfTsKCnRlbXBsYXRlIDxj bGFzcyBUPgp0ZW1wbGF0ZSA8Y2xhc3MgVT4Kdm9pZCBmb288VD46Om1mb28oY29uc3QgVSYpCnsK fQoKdGVtcGxhdGUgPGNsYXNzIFQ+CnZvaWQgdGVzdF9wcm9jKFQgaSkKewogICBmb288ZG91Ymxl PiBmMTsKICAgdHlwZWRlZiBmb288VD4gaWZvbzsKICAgZjEubWZvbyhpKTsKICAgZjEudGVtcGxh dGUgbWZvbzxUPihpKTsKICAgdHlwZWRlZiB0eXBlbmFtZSBpZm9vOjp0ZW1wbGF0ZSBuZXN0ZWQ8 ZG91YmxlPiBib3VuZF90OwogICB0eXBlZGVmIHR5cGVuYW1lIGJvdW5kX3Q6Om90aGVyIG90aGVy OwogICBvdGhlciBvOwogICAodm9pZCkgJm87Cn0KaW50IHRlc3QoKQp7CiAgIHRlc3RfcHJvYygw KTsKICAgcmV0dXJuIDA7Cn0K
reply other threads:[~2003-01-28 19:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030128191654.3729.qmail@sources.redhat.com \ --to=levon@movementarian.org \ --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).