From: Jakub Jelinek <jakub@redhat.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: Jason Merrill <jason@redhat.com>,
Marek Polacek <polacek@redhat.com>,
Richard Biener <rguenther@suse.de>,
Nathaniel Shead <nathanieloshead@gmail.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++: End lifetime of objects in constexpr after destructor call [PR71093]
Date: Tue, 12 Dec 2023 12:15:49 +0100 [thread overview]
Message-ID: <ZXhA5VTvBIFZtU1q@tucnak> (raw)
In-Reply-To: <d01068bc-2789-d9ee-817a-70a77b28f1fe@ispras.ru>
On Tue, Dec 12, 2023 at 02:13:43PM +0300, Alexander Monakov wrote:
>
>
> On Tue, 12 Dec 2023, Jakub Jelinek wrote:
>
> > On Mon, Dec 11, 2023 at 05:00:50PM -0500, Jason Merrill wrote:
> > > In discussion of PR71093 it came up that more clobber_kind options would be
> > > useful within the C++ front-end.
> > >
> > > gcc/ChangeLog:
> > >
> > > * tree-core.h (enum clobber_kind): Rename CLOBBER_EOL to
> > > CLOBBER_STORAGE_END. Add CLOBBER_STORAGE_BEGIN,
> > > CLOBBER_OBJECT_BEGIN, CLOBBER_OBJECT_END.
> > > * gimple-lower-bitint.cc
> > > * gimple-ssa-warn-access.cc
> > > * gimplify.cc
> > > * tree-inline.cc
> > > * tree-ssa-ccp.cc: Adjust for rename.
>
> Doesn't build_clobber_this in the C++ front-end need to be adjusted too?
> I think it is used to place clobbers at start of the ctor (should be
> CLOBBER_OBJECT_BEGIN in the new nomenclature) and end of the dtor (i.e.
> CLOBBER_OBJECT_END).
You're right.
Jakub
next prev parent reply other threads:[~2023-12-12 11:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 1:18 Nathaniel Shead
2023-11-03 1:34 ` Nathaniel Shead
2023-11-27 11:08 ` Nathaniel Shead
2023-12-09 20:12 ` Jason Merrill
2023-12-10 10:22 ` Richard Biener
2023-12-10 11:21 ` Alexander Monakov
2023-12-10 15:58 ` Richard Biener
2023-12-10 18:34 ` Jason Merrill
2023-12-11 8:02 ` Richard Biener
2023-12-11 19:12 ` Jason Merrill
2023-12-11 19:17 ` Richard Biener
2023-12-11 19:21 ` Marek Polacek
2023-12-11 22:00 ` Jason Merrill
2023-12-11 22:22 ` Marek Polacek
2023-12-11 23:03 ` Jakub Jelinek
2023-12-12 11:13 ` Alexander Monakov
2023-12-12 11:15 ` Jakub Jelinek [this message]
2023-12-12 15:24 ` Jason Merrill
2023-12-12 17:50 ` Jason Merrill
2023-12-13 4:40 ` Jason Merrill
2023-12-13 16:47 ` [pushed 1/4] c++: copy location to AGGR_INIT_EXPR Jason Merrill
2023-12-13 16:47 ` [pushed 2/4] c++: constant direct-initialization [PR108243] Jason Merrill
2023-12-13 16:47 ` [pushed 3/4] c++: fix in-charge parm in constexpr Jason Merrill
2023-12-13 16:47 ` [pushed 4/4] c++: End lifetime of objects in constexpr after destructor call [PR71093] Jason Merrill
2023-12-13 18:05 ` [pushed 1/4] c++: copy location to AGGR_INIT_EXPR Patrick Palka
2023-12-13 20:06 ` [pushed] c++: TARGET_EXPR location in default arg [PR96997] Jason Merrill
2023-12-14 0:00 ` [pushed 1/4] c++: copy location to AGGR_INIT_EXPR Marek Polacek
2023-12-14 1:38 ` Jason Merrill
2023-12-14 14:25 ` Marek Polacek
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=ZXhA5VTvBIFZtU1q@tucnak \
--to=jakub@redhat.com \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=nathanieloshead@gmail.com \
--cc=polacek@redhat.com \
--cc=rguenther@suse.de \
/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).