public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "libremax90 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59816] New: [c++11] Incorrect visibility check in template instantiation when the default constructor is a variadic template. Date: Wed, 15 Jan 2014 00:37:00 -0000 [thread overview] Message-ID: <bug-59816-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59816 Bug ID: 59816 Summary: [c++11] Incorrect visibility check in template instantiation when the default constructor is a variadic template. Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: libremax90 at gmail dot com The following C++11 code won't compile on GCC 4.8.2 while clang++ will accept it without a warning. In the following test case, GCC seems to check Base's default constructor visibility in the test function's context, where the templates are instantiated. class Base { protected: template<class... TArgs> Base(TArgs...) {} // Uncomment to workaround //Base() {} }; class Class : public Base { public: template<class... TArgs> Class(TArgs... args) : Base { args... } {} // Another workaround: //Class() {} }; void test() { Class{}; } Here is `g++ -v`'s output: Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.2/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /build/gcc/src/gcc-4.8-20131219/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-cloog-backend=isl --disable-cloog-version-check --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --disable-multilib --disable-werror --enable-checking=release Thread model: posix gcc version 4.8.2 20131219 (prerelease) (GCC)
next reply other threads:[~2014-01-15 0:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-15 0:37 libremax90 at gmail dot com [this message] 2014-01-16 21:41 ` [Bug c++/59816] " daniel.kruegler at googlemail dot com 2015-03-18 20:55 ` paolo.carlini at oracle dot com 2015-03-18 21:30 ` paolo at gcc dot gnu.org 2015-03-18 21:31 ` paolo.carlini at oracle dot com
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-59816-4@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: linkBe 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).