public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 8701b8c92366d2039147b4830657a5bad2cb460f
Date: Fri, 23 Feb 2024 09:52:12 +0000 (GMT)	[thread overview]
Message-ID: <20240223095213.ADD00385840C@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  8701b8c92366d2039147b4830657a5bad2cb460f (commit)
      from  d472f751802f95635997649ea7ec71e4f725aa50 (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 8701b8c92366d2039147b4830657a5bad2cb460f
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Feb 23 10:50:10 2024 +0100

    Document ia64*-*-* obsolescence
    
    The following documents obsoleting of ia64*-*-*.
    
            * gcc-14/changes.html: Document ia64*-*-* obsoleting.

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index c2cdd87a..85ccc54d 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -45,7 +45,10 @@ a work-in-progress.</p>
       <code>-fcf-protection=none</code> needs to be added and then
       with <code>-fcf-protection=xxx</code>.
   </li>
-
+  <li>Support for the <code>ia64*-*-</code> target ports which have been
+      unmaintained for quite a while has been declared obsolete in GCC 14.
+      The next release of GCC will have their sources permanently removed.
+  </li>
 </ul>
 
 

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

Summary of changes:
 htdocs/gcc-14/changes.html | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2024-02-23  9:52 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=20240223095213.ADD00385840C@sourceware.org \
    --to=rguenth@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).