From: Jakub Jelinek <jakub@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH RFA] tree-core: clarify clobber comments
Date: Thu, 14 Mar 2024 21:46:22 +0100 [thread overview]
Message-ID: <ZfNiHsPTw1tg6G24@tucnak> (raw)
In-Reply-To: <20240314202813.2942950-1-jason@redhat.com>
On Thu, Mar 14, 2024 at 04:27:22PM -0400, Jason Merrill wrote:
> OK for trunk?
>
> -- 8< --
>
> It came up on the mailing list that OBJECT_BEGIN/END are described as
> marking object lifetime, but mark the beginning of the constructor and end
> of the destructor, whereas the C++ notion of lifetime is between the end of
> the constructor and beginning of the destructor. So let's fix the comments.
>
> gcc/ChangeLog:
>
> * tree-core.h (enum clobber_kind): Clarify CLOBBER_OBJECT_*
> comments.
LGTM.
> diff --git a/gcc/tree-core.h b/gcc/tree-core.h
> index 8a89462bd7e..654d182b1c3 100644
> --- a/gcc/tree-core.h
> +++ b/gcc/tree-core.h
> @@ -993,9 +993,11 @@ enum clobber_kind {
> CLOBBER_UNDEF,
> /* Beginning of storage duration, e.g. malloc. */
> CLOBBER_STORAGE_BEGIN,
> - /* Beginning of object lifetime, e.g. C++ constructor. */
> + /* Beginning of object data, e.g. start of C++ constructor. This differs
> + from C++ 'lifetime', which starts when initialization is complete; a
> + clobber there would discard the initialization. */
> CLOBBER_OBJECT_BEGIN,
> - /* End of object lifetime, e.g. C++ destructor. */
> + /* End of object data, e.g. end of C++ destructor. */
> CLOBBER_OBJECT_END,
> /* End of storage duration, e.g. free. */
> CLOBBER_STORAGE_END,
>
> base-commit: 5c01ede02a1f9ba1a58ab8d96a73e46e0484d820
> --
> 2.43.2
Jakub
prev parent reply other threads:[~2024-03-14 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 20:27 Jason Merrill
2024-03-14 20:46 ` Jakub Jelinek [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=ZfNiHsPTw1tg6G24@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).