public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Pierre-Marie de Rodat <pmderodat@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-1420] [Ada] Adjust description of Pure_Function pragma Date: Mon, 4 Jul 2022 07:49:41 +0000 (GMT) [thread overview] Message-ID: <20220704074941.B1DB93857B82@sourceware.org> (raw) https://gcc.gnu.org/g:ad7ed87a43655162cbd5765445681870aa99a3a8 commit r13-1420-gad7ed87a43655162cbd5765445681870aa99a3a8 Author: Eric Botcazou <ebotcazou@adacore.com> Date: Mon May 23 09:48:49 2022 +0200 [Ada] Adjust description of Pure_Function pragma The current wording can be read as implying that the result of a call to a pure function does not depend on the context, which is incorrect. The pragma only guarantees the absence of side effects of such a call. gcc/ada/ * doc/gnat_rm/implementation_defined_pragmas.rst (Pure_Function): Fix ambiguous wording about context dependence. * gnat_rm.texi: Regenerate. Diff: --- gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst | 6 +++--- gcc/ada/gnat_rm.texi | 8 ++++---- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst b/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst index af85600f32a..4318a347028 100644 --- a/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst +++ b/gcc/ada/doc/gnat_rm/implementation_defined_pragmas.rst @@ -5504,9 +5504,9 @@ overloaded declaration exists, in which case the pragma applies to all entities). It specifies that the function ``Entity`` is to be considered pure for the purposes of code generation. This means that the compiler can assume that there are no side effects, and -in particular that two calls with identical arguments produce the -same result. It also means that the function can be used in an -address clause. +in particular that two identical calls produce the same result in +the same context. It also means that the function can be used in +an address clause. Note that, quite deliberately, there are no static checks to try to ensure that this promise is met, so ``Pure_Function`` can be used diff --git a/gcc/ada/gnat_rm.texi b/gcc/ada/gnat_rm.texi index a7077e05b47..13cff21288f 100644 --- a/gcc/ada/gnat_rm.texi +++ b/gcc/ada/gnat_rm.texi @@ -21,7 +21,7 @@ @copying @quotation -GNAT Reference Manual , May 24, 2022 +GNAT Reference Manual , Jun 24, 2022 AdaCore @@ -7088,9 +7088,9 @@ overloaded declaration exists, in which case the pragma applies to all entities). It specifies that the function @code{Entity} is to be considered pure for the purposes of code generation. This means that the compiler can assume that there are no side effects, and -in particular that two calls with identical arguments produce the -same result. It also means that the function can be used in an -address clause. +in particular that two identical calls produce the same result in +the same context. It also means that the function can be used in +an address clause. Note that, quite deliberately, there are no static checks to try to ensure that this promise is met, so @code{Pure_Function} can be used
reply other threads:[~2022-07-04 7:49 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220704074941.B1DB93857B82@sourceware.org \ --to=pmderodat@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).