public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97375] New: Unexpected top-level const retainment when declaring non-type template paramter with decltype(auto) Date: Mon, 12 Oct 2020 03:37:16 +0000 [thread overview] Message-ID: <bug-97375-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97375 Bug ID: 97375 Summary: Unexpected top-level const retainment when declaring non-type template paramter with decltype(auto) Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: anders.granlund.0 at gmail dot com Target Milestone: --- Consider the following program: #include <iostream> #include <type_traits> template<const int N> void f1() { std::cout << std::is_const_v<decltype(N)> << std::endl; } template<decltype(auto) N> void f2() { std::cout << std::is_const_v<decltype(N)> << std::endl; } int main() { const int i = 0; f1<i>(); f2<i>(); } When compiling it with -std=c++17 -pedantic-errors it gives the following output: 0 1 I expect it to give the following output instead: 0 0 So that the ignoral of top-level const is done in both cases. Note that clang gives the correct output. Compiler explorer link showing the difference between clang and gcc behaviour: https://godbolt.org/z/aefYKd I tried to report this bug first to clang (with a different example program), but it turned out from the discussion (comment #3) that the bug was actually in gcc: https://bugs.llvm.org/show_bug.cgi?id=47792#c3
next reply other threads:[~2020-10-12 3:37 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-12 3:37 anders.granlund.0 at gmail dot com [this message] 2020-10-12 7:42 ` [Bug c++/97375] " marxin at gcc dot gnu.org 2020-10-14 7:35 ` anders.granlund.0 at gmail dot com 2021-06-09 14:20 ` mpolacek 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-97375-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).