public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. af1de6d37c28c50f4a3ccb659e0bd9dc4ab625d9
Date: Thu, 19 Jan 2023 10:53:11 +0000 (GMT)	[thread overview]
Message-ID: <20230119105311.40B8D3858C52@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  af1de6d37c28c50f4a3ccb659e0bd9dc4ab625d9 (commit)
      from  733c9e4ecbcb5c548863fcf88fc1a5b12e68a2d5 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit af1de6d37c28c50f4a3ccb659e0bd9dc4ab625d9
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date:   Thu Jan 19 11:52:51 2023 +0100

    gcc-13: Announce Solaris 11.3 obsoletion
    
    Here's the changes.html patch corresponding to the Solaris 11.3
    obsoletion notice in
    
            https://gcc.gnu.org/pipermail/gcc/2022-December/240322.html
            https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608384.html

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index ca9cd2da..7047e742 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -32,6 +32,13 @@ a work-in-progress.</p>
     <li>The support for the <code>cr16-elf</code>, <code>tilegx*-linux</code>, <code>tilepro*-linux</code>,
       <code>hppa[12]*-*-hpux10*</code>, <code>hppa[12]*-*-hpux11*</code>
       and <code>m32c-rtems</code> configurations has been removed.</li>
+    <li>Support for Solaris 11.3 (<code>*-*-solaris2.11.3</code>) has been
+      declared obsolete.  The next release of GCC will have corresponding
+      code permanently <strong>removed</strong>.  Details can be found in
+      the
+      <a href="https://gcc.gnu.org/pipermail/gcc/2022-December/240322.html">
+      announcement</a>.
+    </li>
     <li>Support for emitting the STABS debugging format (including the
       <code>-gstabs</code> and <code>-gxcoff</code> options) has been removed.
       (This means the <strong>dbx</strong> debugger is no longer

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-13/changes.html | 7 +++++++
 1 file changed, 7 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-01-19 10:53 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=20230119105311.40B8D3858C52@sourceware.org \
    --to=ro@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).