public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jeroen Wijnhout" <jeroen.wijnhout@gmail.com>
To: "Ian Lance Taylor" <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Explicit template instantiation and -fvisibility. Gcc bug?
Date: Tue, 18 Nov 2008 15:37:00 -0000	[thread overview]
Message-ID: <554ba11a0811180728w128e86f6h4a7cb8fec77af44b@mail.gmail.com> (raw)
In-Reply-To: <m3myfxoy6a.fsf@google.com>

On Tue, Nov 18, 2008 at 4:23 PM, Ian Lance Taylor <iant@google.com> wrote:
> "Jeroen Wijnhout" <jeroen.wijnhout@gmail.com> writes:
>
>> The cause seems to be the instantiation of
>> DependentTemplatedClass<TemplatedClass<int > >, which induces an
>> instantiation of TemplatedClass<int> as well. However I would expect
>> this instantiation to have public visibility as well, because the
>> DependentTemplatedClass instantiation is public. Is this a GCC bug, or
>> am I doing something wrong here?
>
> The semantics of how visibility should work with C++ classes and
> templates are obscure and probably still not fully pinned down.  There
> has been work in each recent gcc release to address this in various
> ways.  You neglected to mention which version of gcc you are using.  I
> would recommend trying your program with mainline (the future gcc
> 4.4).  If it does not behave as you expect, file a bug report (see
> http://gcc.gnu.org/bugs.html ).  Thanks.

I am using GCC4.3.2 (most recent released version afaik), however I
will try the mainline version.

thanks,
Jeroen

  reply	other threads:[~2008-11-18 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17 13:39 Jeroen Wijnhout
2008-11-18 15:29 ` Ian Lance Taylor
2008-11-18 15:37   ` Jeroen Wijnhout [this message]
2008-11-21 12:16     ` J.S.Wijnhout

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=554ba11a0811180728w128e86f6h4a7cb8fec77af44b@mail.gmail.com \
    --to=jeroen.wijnhout@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=jeroen@wijnhout.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).