This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/39242] [4.4 Regression] Inconsistent reject / accept of code
- From: "jason at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Feb 2009 17:39:04 -0000
- Subject: [Bug c++/39242] [4.4 Regression] Inconsistent reject / accept of code
- References: <bug-39242-10053@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #12 from jason at gcc dot gnu dot org 2009-02-19 17:39 -------
(In reply to comment #10)
> What that means is that we *must not* implicitly instantiate things
> declared "extern template" unless they are DECL_DECLARED_INLINE_P. As a
> consequence, at -O3, we cannot implicitly instantiate non-inline "extern
> template" functions.
I'm not entirely sure that's what we want it to say, but it does seem like a
reasonable expectation for users to have.
Beyond this issue, what is the compile speed impact of the earlier change to
use possibly_inlined_p? It seems like it might be making us speculatively
instantiate a lot more functions for potential inlining even at -O1, which I
would expect to cause memory bloat and slower compilation.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39242