public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56272] New: Poor diagnostics for error: specialization of ... after instantiation Date: Sun, 10 Feb 2013 02:22:00 -0000 [thread overview] Message-ID: <bug-56272-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56272 Bug #: 56272 Summary: Poor diagnostics for error: specialization of ... after instantiation Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: ppluzhnikov@google.com Test case: template <typename T> class A { void Invert () { A < double >a; } }; template class A<double>; template <> void A < double >::Invert (); g++ -c t.ii t.ii:11:40: error: specialization of ‘void A<T>::Invert() [with T = double]’ after instantiation Yes, but where was instantiation triggered? In this reduced test case, it's obvious, but in a real test case I have 2MB of text, the code builds fine with gcc-4.7, and the instantiation point is nowhere to be seen.
reply other threads:[~2013-02-10 2:22 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=bug-56272-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: 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).