public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106826] [13 Regression] [modules] Variable template of type trait via importable header gives wrong result
Date: Wed, 21 Sep 2022 12:29:02 +0000	[thread overview]
Message-ID: <bug-106826-4-pxQHdnLbDQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106826-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106826

Patrick Palka <ppalka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |ppalka at gcc dot gnu.org
             Status|UNCONFIRMED                 |ASSIGNED
                 CC|                            |ppalka at gcc dot gnu.org
     Ever confirmed|0                           |1
   Target Milestone|---                         |13.0
   Last reconfirmed|                            |2022-09-21

--- Comment #2 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Confirmed, likely started with r13-2351-g33005a4be49466 though it's ultimately
a latent modules bug.  Reduced testcase:

$ cat 106826_a.C
export module pr106826;
template<class T> constexpr bool is_lvalue_reference_v = false;
template<class T> constexpr bool is_lvalue_reference_v<T&> = true;
$ cat 106826_b.C
module pr106826;
static_assert(is_lvalue_reference_v<int&>);
$ g++ -fmodules-ts 106826_a.C
$ g++ -fmodules-ts 106826_b.C
106826_b.C:2:15: error: static assertion failed

It looks variable template partial specializations get lost during streaming.

  parent reply	other threads:[~2022-09-21 12:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 17:57 [Bug c++/106826] New: " johelegp at gmail dot com
2022-09-05 18:59 ` [Bug c++/106826] [13 Regression] " johelegp at gmail dot com
2022-09-21 12:29 ` ppalka at gcc dot gnu.org [this message]
2022-09-22  5:04 ` johelegp at gmail dot com
2022-09-22 12:47 ` cvs-commit at gcc dot gnu.org
2022-09-22 12:56 ` ppalka at gcc dot gnu.org
2022-09-22 12:57 ` ppalka at gcc dot gnu.org
2022-09-22 14:08 ` johelegp at gmail dot com
2022-09-25 17:14 ` johelegp at gmail 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-106826-4-pxQHdnLbDQ@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: link
Be 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).