public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98360] sizeof in template difference between g++/icc and clang++ Date: Fri, 26 Nov 2021 01:48:15 +0000 [thread overview] Message-ID: <bug-98360-4-lLL00JtyHL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98360-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98360 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- GCC, ICC and MSVC all agree that this is valid code and all produce 4. clang is the only one which rejects it. Here is an even more reduced testcase: template <typename T> struct uintset { T values[1]; struct traits { }; struct hash : traits { int foo () { return sizeof (uintset::values); } }; hash h; }; uintset<int> s; int x = s.h.foo (); If you remove the base class or change it not to dependent type, the code is accepted. The defect reports in this area: http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#613 http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#198 http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2253.html is the paper which resolves 613. I suspect GCC is correct if I go by this paper.
prev parent reply other threads:[~2021-11-26 1:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-17 18:47 [Bug c++/98360] New: " jakub at gcc dot gnu.org 2020-12-18 23:52 ` [Bug c++/98360] " ensadc at mailnesia dot com 2020-12-19 1:35 ` ensadc at mailnesia dot com 2021-11-26 1:48 ` pinskia at gcc dot gnu.org [this message]
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-98360-4-lLL00JtyHL@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).