public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/47693] New: warning flag for emission of vague linkage bits
@ 2011-02-11 1:26 bkoz at gcc dot gnu.org
2011-02-11 1:43 ` [Bug c++/47693] " pinskia at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: bkoz at gcc dot gnu.org @ 2011-02-11 1:26 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47693
Summary: warning flag for emission of vague linkage bits
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: bkoz@gcc.gnu.org
Request for -Wvague-linkage.
This flag would warn for the lack of key function, etc that makes
typeinfo/vtable information emitted in every TU for polymorphic classes
class regex_error
: public std::runtime_error
{
public:
explicit
regex_error(regex_constants::error_type __ecode)
: std::runtime_error("regex_error"), _M_code(__ecode)
{ }
regex_constants::error_type
code() const
{ return _M_code; }
protected:
regex_constants::error_type _M_code;
};
It's hard to scan through the libstdc++ sources for other places where
maintainers might want to know exact linkage. However, the compiler already
knows this.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-02-11 1:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-11 1:26 [Bug c++/47693] New: warning flag for emission of vague linkage bits bkoz at gcc dot gnu.org
2011-02-11 1:43 ` [Bug c++/47693] " pinskia at gcc dot gnu.org
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).