From: Jody Winston <jody@sccsi.com>
To: egcs@cygnus.com
Subject: Explicit Template Expansion syntax
Date: Wed, 10 Dec 1997 10:46:00 -0000 [thread overview]
Message-ID: <199712101825.MAA12309@friday.sccsi.com> (raw)
On SGI Irix 6.2 using egcs-1.00 release I'm having problems with
undefined symbols when using templates. I've added explicit template
expansion for most cases, but I'm having syntax problems with the
following two examples:
ld: ERROR 33: Unresolved text symbol "CppParse_ListT<CppParse_Interface, ilu_interface_s *>::CppParse_ListT(list_s *)" -- 1st referenced by cppmain.o.
I tried:
template class CppParse_ListT<CppParse_Interface, ilu_interface_s *>;
but this failed with the same unresolved symbol.
also I tried:
template class CppParse_ListT<CppParse_Interface, ilu_interface_s *>::CppParse_ListT(list_s *);
but this fails with cppmain.cc:89: parse error before `*'.
If I try the following:
char const * getCacheKey<CppParseName_TypeUsage>(CppParseName_TypeUsage, CppParseName_Scope const *, CppParseName_Scope const *);
The following message from as are generated:
as: Error: /tmp/cca004yi.s, line 4823: stmt extends past logical end
la $25,^PC<^P
as: Error: /tmp/cca004yi.s, line 5140: stmt extends past logical end
.globl ^PC<^P
as: Error: /tmp/cca004yi.s, line 5141: stmt extends past logical end
.ent ^PC<^P
as: Error: /tmp/cca004yi.s, line 5142: undefined assembler operation: ^P
^PC<^P:
as: Error: /tmp/cca004yi.s, line 5158: ')' expected: gp_rel
lui $1,%hi(%neg(%gp_rel(^PC<^P)))
as: Error: /tmp/cca004yi.s, line 5159: ')' expected: gp_rel
addiu $1,$1,%lo(%neg(%gp_rel(^PC<^P)))
as: Error: /tmp/cca004yi.s, line 5377: stmt extends past logical end
.end ^PC<^P
as: Error: /tmp/cca004yi.s, line 9562: stmt extends past logical end
la $25,^PC<^P
gmake: *** [cppparsename.o] Error 1
reply other threads:[~1997-12-10 10:46 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=199712101825.MAA12309@friday.sccsi.com \
--to=jody@sccsi.com \
--cc=egcs@cygnus.com \
/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).