From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH] wwwdocs: Note that old reload is deprecated
Date: Thu, 5 Jan 2023 19:27:40 +0000 [thread overview]
Message-ID: <febe8136ba2e1afbbf70beff8ce0a1cf66401dff.1672946731.git.segher@kernel.crashing.org> (raw)
Hi!
Happy new year everyone.
Is this patch okay to commit?
Segher
---
htdocs/gcc-13/changes.html | 2 ++
1 file changed, 2 insertions(+)
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 3876ad77543a..954469cdcfa4 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -39,6 +39,8 @@ a work-in-progress.</p>
<li>Legacy debug info compression option <code>-gz=zlib-gnu</code> was removed
and the option is ignored right now.</li>
<li>New debug info compression option value <code>-gz=zstd</code> has been added.</li>
+ <li>Support for old reload is deprecated. It will be removed in a future
+ release. Every target will always use LRA from then on.</li>
</ul>
--
1.8.3.1
next reply other threads:[~2023-01-05 19:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 19:27 Segher Boessenkool [this message]
2023-01-05 19:54 ` Paul Koning
2023-01-05 20:23 ` Segher Boessenkool
2023-01-11 14:21 ` Gerald Pfeifer
2023-01-11 14:34 ` Richard Biener
2023-01-11 15:15 ` Segher Boessenkool
2023-01-11 16:27 ` Richard Biener
2023-01-11 18:32 ` Segher Boessenkool
2023-01-11 18:39 ` Richard Biener
2023-01-11 19:07 ` Segher Boessenkool
2023-01-12 7:44 ` Richard Biener
2023-01-12 7:48 ` Richard Biener
2023-01-11 18:42 ` Paul Koning
2023-01-11 19:28 ` Segher Boessenkool
2023-01-11 22:07 ` Paul Koning
2023-01-12 9:50 ` Segher Boessenkool
2023-01-12 14:17 ` Paul Koning
2023-01-12 14:40 ` Segher Boessenkool
2023-01-12 15:07 ` Paul Koning
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=febe8136ba2e1afbbf70beff8ce0a1cf66401dff.1672946731.git.segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--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).