public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] wwwdocs: Announce Solaris 11.3 obsoletion
Date: Thu, 19 Jan 2023 13:22:49 +0100	[thread overview]
Message-ID: <ydd5yd2soh2.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <1875a6a3-ea37-f694-9299-4ffea48934eb@pfeifer.com> (Gerald Pfeifer's message of "Thu, 19 Jan 2023 11:27:47 +0100 (CET)")

[-- Attachment #1: Type: text/plain, Size: 449 bytes --]

Hi Gerald,

>> Btw., I noticed the -gz=zstd addition is listed under Caveats.  I don't
>> think this belongs here and probably only landed due to the -gz=zlib-gnu
>> removal above.
>
> Agreed. Can you address this on the way?

sure: done like so:

	gcc-13: Move -gz=zstd to General Improvements

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University



[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gz-zstd.patch --]
[-- Type: text/x-patch, Size: 1115 bytes --]

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 7047e742..ba42170c 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -45,7 +45,6 @@ a work-in-progress.</p>
       supported, either.)</li>
     <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><code>-Warray-bounds=2</code> will no longer issue warnings for out of
       bounds accesses to trailing struct members of one-element array type
       anymore. Instead it diagnoses accesses to trailing arrays according to
@@ -107,6 +106,7 @@ a work-in-progress.</p>
     AddressSanitizer defaults to <code>detect_stack_use_after_return=1</code> on GNU/Linux targets.
     For compatibility, it can be disabled with <code>env ASAN_OPTIONS=detect_stack_use_after_return=0</code>.
   </li>
+  <li>New debug info compression option value <code>-gz=zstd</code> has been added.</li>
   <li>
     Link-time optimization improvements:
     <ul>

      reply	other threads:[~2023-01-19 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 14:06 Rainer Orth
2023-01-19 10:27 ` Gerald Pfeifer
2023-01-19 12:22   ` Rainer Orth [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=ydd5yd2soh2.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).