From: Joseph Myers <joseph@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Jakub Jelinek <jakub@redhat.com>, <gcc-patches@gcc.gnu.org>,
Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PING] options: Clarify 'Init' option property usage for streaming optimization (was: [PATCH] options, lto: Optimize streaming of optimization nodes)
Date: Wed, 26 Oct 2022 18:21:07 +0000 [thread overview]
Message-ID: <36c2211d-dd3e-24ef-7f53-b664a8aeda7e@codesourcery.com> (raw)
In-Reply-To: <87eduud7eg.fsf@dem-tschwing-1.ger.mentorg.com>
On Wed, 26 Oct 2022, Thomas Schwinge wrote:
> Hi!
>
> Ping. For convenience, I've re-attached
> "options: Clarify 'Init' option property usage for streaming optimization".
> (I've re-verified: "No functional change; no change in generated files.")
OK.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-10-26 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 8:33 [PATCH] options, lto: Optimize streaming of optimization nodes Jakub Jelinek
2020-09-14 6:39 ` Richard Biener
2020-09-14 7:00 ` Jakub Jelinek
2020-09-14 7:31 ` Richard Biener
2020-09-14 8:48 ` Jakub Jelinek
2020-09-14 9:02 ` Jan Hubicka
2020-09-14 9:47 ` Jakub Jelinek
2020-10-05 9:21 ` Patch ping (Re: [PATCH] options, lto: Optimize streaming of optimization nodes) Jakub Jelinek
2020-11-18 9:36 ` [PATCH] options, lto: Optimize streaming of optimization nodes Jakub Jelinek
2020-11-18 19:06 ` Joseph Myers
2022-03-31 13:22 ` options: Clarify 'Init' option property usage for streaming optimization (was: [PATCH] options, lto: Optimize streaming of optimization nodes) Thomas Schwinge
2022-10-26 13:46 ` [PING] " Thomas Schwinge
2022-10-26 18:21 ` Joseph Myers [this message]
2020-09-14 9:23 ` [PATCH] options, lto: Optimize streaming of optimization nodes Richard Biener
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=36c2211d-dd3e-24ef-7f53-b664a8aeda7e@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
--cc=thomas@codesourcery.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).