public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan at twosigma dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105344] New: std::source_location::curent() seemingly treated as a pure function in template specializations Date: Fri, 22 Apr 2022 10:11:27 +0000 [thread overview] Message-ID: <bug-105344-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105344 Bug ID: 105344 Summary: std::source_location::curent() seemingly treated as a pure function in template specializations Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jan at twosigma dot com Target Milestone: --- When using std::source_location::current().line() in certain contexts on two different lines, gcc seems to incorrectly think the expression refers to the same value. Testcase: #include <source_location> #include <utility> template <int i, class = void> struct foo; // Two following two specializations are different, yet gcc errors out, // claiming they are the same. template <int i> struct foo<i, std::enable_if_t<i == std::source_location::current().line()>> { static constexpr int num = i; }; template <int i> struct foo<i, std::enable_if_t<i == std::source_location::current().line()>> { static constexpr int num = i; }; This outputs: <source>:14:8: error: redefinition of 'struct foo<i, typename std::enable_if<(i == std::source_location::current().std::source_location::line()), void>::type>' 14 | struct foo<i, std::enable_if_t<i == std::source_location::current().line()>> { | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <source>:9:8: note: previous definition of 'struct foo<i, typename std::enable_if<(i == std::source_location::current().std::source_location::line()), void>::type>' 9 | struct foo<i, std::enable_if_t<i == std::source_location::current().line()>> { | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Compiler returned: 1 https://godbolt.org/z/ozf1MbG3n shows this code works fine under MSVC.
next reply other threads:[~2022-04-22 10:11 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-22 10:11 jan at twosigma dot com [this message] 2022-11-02 20:27 ` [Bug c++/105344] " pinskia 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-105344-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).