public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/60854] [4.9/4.10 Regression] inline constructor of extern template
Date: Wed, 16 Apr 2014 08:32:00 -0000 [thread overview]
Message-ID: <bug-60854-4-54cixbfgkh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60854-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60854
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-04-16
CC| |hubicka at gcc dot gnu.org
Component|c++ |ipa
Target Milestone|--- |4.9.1
Summary|inline constructor of |[4.9/4.10 Regression]
|extern template |inline constructor of
| |extern template
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Not sure how the C++ 'extern template' explicit instantiation interacts with
the GCC always-inline extension. But with always-inline it is an _error_
to have a function not inlined and thus we omit the body of the function.
Somehow early inlining doesn't see that MyClass::MyClass is always-inline,
this works in 4.8 and the constructor is always-inlined.
Honza?
next prev parent reply other threads:[~2014-04-16 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 21:21 [Bug c++/60854] New: " joachim.schoeberl at tuwien dot ac.at
2014-04-16 8:32 ` rguenth at gcc dot gnu.org [this message]
2014-04-16 21:06 ` [Bug ipa/60854] [4.9/4.10 Regression] " hubicka at gcc dot gnu.org
2014-04-17 2:23 ` hubicka at gcc dot gnu.org
2014-04-17 8:10 ` [Bug ipa/60854] [4.9 " rguenth at gcc dot gnu.org
2014-05-17 22:19 ` hubicka at gcc dot gnu.org
2014-06-26 13:01 ` rguenth at gcc dot gnu.org
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=bug-60854-4-54cixbfgkh@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).