public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: janis187@us.ibm.com To: gcc-gnats@gcc.gnu.org Subject: target/9681: powerpc64 -frepo fails to instantiate some templates Date: Wed, 12 Feb 2003 23:46:00 -0000 [thread overview] Message-ID: <20030212233713.29741.qmail@sources.redhat.com> (raw) >Number: 9681 >Category: target >Synopsis: powerpc64 -frepo fails to instantiate some templates >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Feb 12 23:46:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Janis Johnson >Release: 3.3 20030210 (prerelease) >Organization: >Environment: powerpc64-linux; SuSE SLES8 >Description: Five tests in g++.old-deja/g++.pt (instantiate[46].C and repo[124].C) fail because some templates are not instantiated with -frepo. This affects powerpc64-linux, both cross compilers and native 64-bit compilers, for mainline, 3.3-branch, and 3.2-branch. Here's what happens with test repo1.C: % g++ -c -frepo repo1.C % g++ -frepo repo1.o repo1.o: In function `.main': repo1.o(.text+0x18): undefined reference to `.void g<int>(int)' collect2: ld returned 1 exit status That test: template <class T> struct A { virtual ~A () { } }; template <class T> void g (T t) { } template class A<int>; int main () { g (42); } >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-02-12 23:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-12 23:46 janis187 [this message] 2003-02-19 16:15 target/9681: [powerpc64] " dje 2003-02-25 11:06 target/9681: powerpc64 " Alan Modra 2003-02-26 4:56 Jim Wilson
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=20030212233713.29741.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --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).