public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Marc Poulhi?s <dkm@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-1196] ada: Fix obsolete comment in Sinfo.Utils Date: Thu, 25 May 2023 08:04:28 +0000 (GMT) [thread overview] Message-ID: <20230525080428.E632C3858422@sourceware.org> (raw) https://gcc.gnu.org/g:825cb651135ad9ddb28e047b81ea8a2a6c08a75f commit r14-1196-g825cb651135ad9ddb28e047b81ea8a2a6c08a75f Author: Bob Duff <duff@adacore.com> Date: Thu Mar 2 09:44:03 2023 -0500 ada: Fix obsolete comment in Sinfo.Utils ...caused by moving code here from Atree. gcc/ada/ * sinfo-utils.adb: Update comment to refer to New_Node_Debugging_Output. Diff: --- gcc/ada/sinfo-utils.adb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/ada/sinfo-utils.adb b/gcc/ada/sinfo-utils.adb index 02ed69d7136..b0cc2d3b418 100644 --- a/gcc/ada/sinfo-utils.adb +++ b/gcc/ada/sinfo-utils.adb @@ -50,7 +50,7 @@ package body Sinfo.Utils is -- Either way, gnat1 will stop when node 12345 is created, or certain other -- interesting operations are performed, such as Rewrite. To see exactly - -- which operations, search for "pragma Debug" below. + -- which operations, search for "New_Node_Debugging_Output" in Atree. -- The second method is much faster if the amount of Ada code being -- compiled is large.
reply other threads:[~2023-05-25 8:04 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=20230525080428.E632C3858422@sourceware.org \ --to=dkm@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).