public inbox for
help / color / mirror / Atom feed
From: Siddhesh Poyarekar <>
Subject: gcc-wwwdocs branch master updated. 829c505d5214d300cd4d5c67bdd6041f7128e3fc
Date: Thu, 27 Jan 2022 10:45:00 +0000 (GMT)	[thread overview]
Message-ID: <> (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  829c505d5214d300cd4d5c67bdd6041f7128e3fc (commit)
      from  956e42549676172be23a0a3e11d98fc0b9e8b340 (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 829c505d5214d300cd4d5c67bdd6041f7128e3fc
Author: Siddhesh Poyarekar <>
Date:   Thu Jan 27 15:57:19 2022 +0530

    Document __builtin_dynamic_object_size addition for GCC 12
    Signed-off-by: Siddhesh Poyarekar <>

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index c69b301e..c6baee75 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -157,6 +157,8 @@ a work-in-progress.</p>
   <li>A new built-in function, <code>__builtin_assoc_barrier</code>, was added.
       It can be used to inhibit re-association of floating-point
+  <li>Support for <code>__builtin_dynamic_object_size</code> compatible with
+      the clang language extension was added.</li>
   <li>New warnings:
       <li><code>-Wbidi-chars</code> warns about potentially misleading UTF-8


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


                 reply	other threads:[~2022-01-27 10:45 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).