This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: LTO, shared libraries and extern class templates

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: grasland at lal dot in2p3 dot fr
Cc: gcc-help <gcc-help at gcc dot gnu dot org>
Date: Thu, 11 Oct 2018 17:14:45 +0100
Subject: Re: LTO, shared libraries and extern class templates
References: <0a855481-a493-34a4-1256-f7a10db36e14@lal.in2p3.fr> <CAH6eHdTDMmNVWTi5gsADC_kjbAQoV7XzD1UPNNnZq0mSTx2U=g@mail.gmail.com> <19ec519d-fa0a-4426-b02a-3a502c9311e9@lal.in2p3.fr>

On Thu, 11 Oct 2018 at 17:12, Hadrien Grasland wrote:
> Thanks for clarifying that explicit class template instantiations should work. Trying to produce a minimal reproducer was a very interesting exercise. As it turns out, the problematic situation which I am experiencing does not occur with explicit template instantiations per se, but only when those are combined with inheritance in a certain way.

Which is why that should be the *first* thing you do. It saves everybody's time.

I'll look at the example code properly ASAP.

References:
- LTO, shared libraries and extern class templates
  - From: Hadrien Grasland
- Re: LTO, shared libraries and extern class templates
  - From: Jonathan Wakely
- Re: LTO, shared libraries and extern class templates
  - From: Hadrien Grasland

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]