public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kutdanila at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95950] New: Call to pseudo-destructor does not end the lifetime until C++20
Date: Sun, 28 Jun 2020 20:27:26 +0000	[thread overview]
Message-ID: <bug-95950-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95950
           Summary: Call to pseudo-destructor does not end the lifetime
                    until C++20
           Product: gcc
           Version: 9.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kutdanila at yandex dot ru
  Target Milestone: ---

#include <optional>

int main() {
  std::optional<int> t = 2;
  using T = std::optional<int>;
  t.~T();
  return t.has_value();
}

g++ test.cpp -O1 -o test


This code should not return 0 until C++20, see
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p0593r4.html and
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p0593r4.html#c5-c-and-iso-c-2017-diffcpp17

In that case, std::optional<int> has a trivial destructor and should have no
effect

The regression started somewhere in the 9th version of gcc in any optimized
builds (O1-O3, with O0 still ok)

Yet, static_assert works fine

#include <optional>

int main() {
  constexpr std::optional<int> t = 2;
  using T = std::optional<int>;
  t.~T();
  static_assert(t.has_value());
}

             reply	other threads:[~2020-06-28 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-28 20:27 kutdanila at yandex dot ru [this message]
2020-06-28 20:38 ` [Bug c++/95950] " kutdanila at yandex dot ru
2020-06-28 21:02 ` 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-95950-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).