From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2] Improve compute_control_dep_chain documentation
Date: Fri, 26 Aug 2022 10:19:19 -0600 [thread overview]
Message-ID: <ebff728b-a299-e998-ed00-6aae9d9516d9@gmail.com> (raw)
In-Reply-To: <20220826123409.524BF13A7E@imap2.suse-dmz.suse.de>
On 8/26/2022 6:34 AM, Richard Biener via Gcc-patches wrote:
> In the quest to understand how compute_control_dep_chain works I've
> produced the following two changes, documenting PR106754 on the
> way.
>
> Bootstrap and regtest is running on x86_64-unknown-linux-gnu,
> the changes should be no-ops but hopefully improve understanding
> of the code.
Thanks so much for this. Every time I've had to get into that code it
makes my head hurt -- anything that clarifies is an improvement.
Jeff
prev parent reply other threads:[~2022-08-26 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 12:34 Richard Biener
2022-08-26 16:19 ` Jeff Law [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=ebff728b-a299-e998-ed00-6aae9d9516d9@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).