public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alex Coplan <alex.coplan@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: Jason Merrill <jason@redhat.com>,
	Marek Polacek <polacek@redhat.com>,
	Joseph Myers <josmyers@redhat.com>,
	Iain Sandoe <iain@sandoe.co.uk>
Subject: [PATCH] wwwdocs: Add note to changes.html for __has_{feature,extension}
Date: Thu, 4 Apr 2024 11:00:51 +0100	[thread overview]
Message-ID: <Zg56U+SNee6eoQJS@arm.com> (raw)

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

Hi,

This adds a note to the GCC 14 release notes mentioning support for
__has_{feature,extension} (PR60512).

OK to commit?

Thanks,
Alex

[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 658 bytes --]

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 9fd224c1..facead8d 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -242,6 +242,12 @@ a work-in-progress.</p>
       <code>constinit</code> and optimized dynamic initialization</li>
     </ul>
   </li>
+  <li>The Clang language extensions <code>__has_feature</code> and
+    <code>__has_extension</code> have been implemented in GCC.  These
+    are available from C, C++, and Objective-C(++).
+    This is primarily intended to aid the portability of code written
+    against Clang.
+  </li>
 </ul>
 
 <h4 id="libstdcxx">Runtime Library (libstdc++)</h4>

             reply	other threads:[~2024-04-04 10:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 10:00 Alex Coplan [this message]
2024-04-15 10:13 ` Alex Coplan
2024-04-15 20:22   ` Eric Gallager
2024-04-17 15:41   ` Marek Polacek
2024-04-26 10:12     ` Alex Coplan
2024-04-26 13:14       ` Marek Polacek
2024-04-26 13:31         ` Alex Coplan
2024-05-01 11:27         ` Gerald Pfeifer

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=Zg56U+SNee6eoQJS@arm.com \
    --to=alex.coplan@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=jason@redhat.com \
    --cc=josmyers@redhat.com \
    --cc=polacek@redhat.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).