public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ldalessandro at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99859] New: constexpr evaluation with member function is incorrect
Date: Wed, 31 Mar 2021 22:54:10 +0000 [thread overview]
Message-ID: <bug-99859-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99859
Bug ID: 99859
Summary: constexpr evaluation with member function is incorrect
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ldalessandro at gmail dot com
Target Milestone: ---
I'm at a loss for how to describe this.
I have an intrusive reference counting smart pointer that manipulates the
pointed-to object's `count_` member either explicitly or via a member function.
The explicit version works fine, the member function does not (both are fine in
clang).
See the difference with -DUSE_DEC in https://godbolt.org/z/rhb7e6rjr.
next reply other threads:[~2021-03-31 22:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 22:54 ldalessandro at gmail dot com [this message]
2021-03-31 23:15 ` [Bug c++/99859] " ldalessandro at gmail dot com
2021-04-01 10:29 ` jakub at gcc dot gnu.org
2021-04-01 14:15 ` jakub at gcc dot gnu.org
2021-04-07 11:39 ` jakub at gcc dot gnu.org
2021-04-07 12:05 ` ppalka at gcc dot gnu.org
2021-04-07 12:14 ` jakub at gcc dot gnu.org
2021-04-07 12:15 ` ppalka at gcc dot gnu.org
2021-04-07 12:24 ` jakub at gcc dot gnu.org
2021-04-07 12:45 ` ppalka at gcc dot gnu.org
2021-04-07 13:38 ` jakub at gcc dot gnu.org
2021-04-07 13:44 ` jakub at gcc dot gnu.org
2021-04-07 13:48 ` jakub at gcc dot gnu.org
2021-04-07 14:04 ` jakub at gcc dot gnu.org
2021-04-07 16:32 ` ppalka at gcc dot gnu.org
2021-04-07 17:33 ` jakub at gcc dot gnu.org
2021-04-08 15:19 ` cvs-commit at gcc dot gnu.org
2021-04-08 15:21 ` jakub at gcc dot gnu.org
2021-04-08 15:22 ` jakub at gcc dot gnu.org
2021-04-19 1:53 ` ppalka at gcc dot gnu.org
2021-04-20 9:45 ` cvs-commit at gcc dot gnu.org
2021-07-28 22:16 ` pinskia at gcc dot gnu.org
2021-08-28 21:17 ` pinskia at gcc dot gnu.org
2021-08-28 21:21 ` pinskia at gcc dot gnu.org
2022-02-02 17:29 ` redi 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-99859-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: 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).