public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marek Polacek <polacek@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
	Tobias Burnus <tobias@codesourcery.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] wwwdocs: Document several further C++23 changes
Date: Thu, 2 Mar 2023 08:30:34 -0500	[thread overview]
Message-ID: <ZACk+jlmdC3t86nk@redhat.com> (raw)
In-Reply-To: <ZACMogsrU0vpmQ1S@tucnak>

On Thu, Mar 02, 2023 at 12:46:42PM +0100, Jakub Jelinek wrote:
> Hi!
> 
> Tobias mentioned on IRC that assume attribute wasn't mentioned in
> changes.html.  The P1774R8 entry was missing for C++, so I went through
> projects/cxx-status.html#cxx23 and filled in all the missing papers
> which have been implemented newly in GCC 13, plus a small note for C family
> about assume attribute.
> 
> Ok for wwwdocs?

Sure, thanks.
 
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> index 410594ae..839b73d0 100644
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -182,6 +182,10 @@ a work-in-progress.</p>
>      <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a>
>      to detect misuses of file descriptors.
>    </li>
> +  <li>A new statement attribute for C++23 <a href="https://wg21.link/p1774r8">P1774R8</a> Portable
> +      assumptions support also in C or older C++:
> +    <a href="https://gcc.gnu.org/onlinedocs/gcc/Statement-Attributes.html#index-assume-statement-attribute"><code>__attribute__((assume(EXPR)));</code>
> +  </li>
>  </ul>
>  
>  <h3 id="c">C</h3>
> @@ -290,6 +294,29 @@ a work-in-progress.</p>
>  	Operator You Are Looking For
>  	(<a href="https://gcc.gnu.org/PR106644">PR106644</a>)
>        </li>
> +      <li> <a href="https://wg21.link/p2362r3">P2362R3</a>, Remove non-encodable
> +          wide character literals and multicharacter wide character literals
> +	(<a href="https://gcc.gnu.org/PR106647">PR106647</a>)
> +      </li>
> +      <li> <a href="https://wg21.link/p2448r2">P2448R2</a>, Relaxing some
> +          constexpr restrictions
> +	(<a href="https://gcc.gnu.org/PR106649">PR106649</a>)
> +      </li>
> +      <li> <a href="https://wg21.link/p1467r9">P1467R9</a>, Extended
> +          floating-point types and standard names
> +	(<a href="https://gcc.gnu.org/PR106652">PR106652</a>)
> +      </li>
> +      <li> <a href="https://wg21.link/p1774r8">P1774R8</a>, Portable
> +          assumptions
> +	(<a href="https://gcc.gnu.org/PR106654">PR106654</a>)
> +      </li>
> +      <li> <a href="https://wg21.link/p2295r6">P2295R6</a>, Support for
> +          UTF-8 as a portable source file encoding
> +	(<a href="https://gcc.gnu.org/PR106655">PR106655</a>)
> +      </li>
> +      <li> <a href="https://wg21.link/p2589r1">P2589R1</a>, static operator[]
> +	(<a href="https://gcc.gnu.org/PR107684">PR107684</a>)
> +      </li>
>      </ul>
>    </li>
>    <li>New warnings:
> 
> 	Jakub
> 

Marek


  reply	other threads:[~2023-03-02 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 11:46 Jakub Jelinek
2023-03-02 13:30 ` Marek Polacek [this message]
2023-03-03 22:59 ` Gerald Pfeifer
2023-03-03 23:07 ` 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=ZACk+jlmdC3t86nk@redhat.com \
    --to=polacek@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jakub@redhat.com \
    --cc=tobias@codesourcery.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).