public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98675] Accessing member of temporary outside its lifetime allowed in constexpr function
Date: Wed, 26 Jul 2023 01:45:41 +0000	[thread overview]
Message-ID: <bug-98675-4-GAvP56tUZl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98675-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:9fdbd7d6fa5e0a76898dd66658934e3184111680

commit r14-2773-g9fdbd7d6fa5e0a76898dd66658934e3184111680
Author: Nathaniel Shead <nathanieloshead@gmail.com>
Date:   Sun Jul 23 01:15:14 2023 +1000

    c++: Track lifetimes in constant evaluation [PR70331,PR96630,PR98675]

    This adds rudimentary lifetime tracking in C++ constexpr contexts,
    allowing the compiler to report errors with using values after their
    backing has gone out of scope. We don't yet handle other ways of
    accessing values outside their lifetime (e.g. following explicit
    destructor calls).

            PR c++/96630
            PR c++/98675
            PR c++/70331

    gcc/cp/ChangeLog:

            * constexpr.cc (constexpr_global_ctx::is_outside_lifetime): New
            function.
            (constexpr_global_ctx::get_value): Don't return expired values.
            (constexpr_global_ctx::get_value_ptr): Likewise.
            (constexpr_global_ctx::remove_value): Mark value outside
            lifetime.
            (outside_lifetime_error): New function.
            (cxx_eval_call_expression): No longer track save_exprs.
            (cxx_eval_loop_expr): Likewise.
            (cxx_eval_constant_expression): Add checks for outside lifetime
            values. Remove local variables at end of bind exprs, and
            temporaries after cleanup points.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp1y/constexpr-lifetime1.C: New test.
            * g++.dg/cpp1y/constexpr-lifetime2.C: New test.
            * g++.dg/cpp1y/constexpr-lifetime3.C: New test.
            * g++.dg/cpp1y/constexpr-lifetime4.C: New test.
            * g++.dg/cpp1y/constexpr-lifetime5.C: New test.
            * g++.dg/cpp1y/constexpr-lifetime6.C: New test.

    Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>

      parent reply	other threads:[~2023-07-26  1:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 11:53 [Bug c++/98675] New: " redi at gcc dot gnu.org
2021-01-14 14:31 ` [Bug c++/98675] " mpolacek at gcc dot gnu.org
2022-01-31  4:23 ` tobi at gcc dot gnu.org
2022-01-31  4:35 ` tobi at gcc dot gnu.org
2022-01-31  4:43 ` pinskia at gcc dot gnu.org
2022-01-31 11:44 ` tobi at gcc dot gnu.org
2023-05-26 15:00 ` pinskia at gcc dot gnu.org
2023-07-26  1:45 ` cvs-commit at gcc dot gnu.org [this message]

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-98675-4-GAvP56tUZl@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).