public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 1e978400c2a88a20e13031016db5c2746452ff54 Date: Thu, 14 May 2020 14:14:39 +0000 (GMT) [thread overview] Message-ID: <20200514141439.B6F1E395CCE5@sourceware.org> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 3024 bytes --] 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 1e978400c2a88a20e13031016db5c2746452ff54 (commit) from f690b0e7ee74f7411a0380ef9ed1bc941cd6d3a7 (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 1e978400c2a88a20e13031016db5c2746452ff54 Author: Iain Buclaw <ibuclaw@gdcproject.org> Date: Tue Apr 28 01:00:09 2020 +0200 wwwdocs: Add D front-end section for GCC 10 changes diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index 8eaa3326..0daa5ef7 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -497,6 +497,41 @@ int get_naïve_pi() { </li> </ul> +<h3 id="d">D</h3> +<ul> + <li>Support for <code>static foreach</code> has been implemented.</li> + <li>Aliases can now be created directly from any <code>__trait</code> that + return symbols or tuples. Previously, an <code>AliasSeq</code> was + necessary in order to alias their return. + </li> + <li>It is now possible to detect the language ABI specified for a struct, + class, or interface using <code>__traits(getLinkage, ...)</code> + <li>Support for <code>core.math.toPrec</code> intrinsics have been added. + These intrinsics guarantee the rounding to specific floating-point + precisions at required points in the code. + </li> + <li>Support for <code>pragma(inline)</code> has been implemented. Previously + the pragma was recognized, but had no effect on the compilation. + </li> + <li>Optional parentheses in <code>asm</code> operands are now deprecated and + will be removed in a future release. + </li> + <li>All content imported files are now included in the make dependency list + when compiling with <code>-M</code>. + </li> + <li>Compiler recognized attributes provided by the <code>gcc.attribute</code> + module will now take effect when applied to function prototypes as well + as when applied to full function declarations. + </li> + <li>Added <code>--enable-libphobos-checking</code> configure option to + control whether run-time checks are compiled into the D runtime library. + </li> + <li>Added <code>--with-libphobos-druntime-only</code> configure option to + allow specifying whether to build only the core D runtime library, or + both the core and standard libraries into libphobos. + </li> +</ul> + <h3 id="fortran">Fortran</h3> <ul> <li><code>use_device_addr</code> of version 5.0 of the ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-05-14 14:14 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=20200514141439.B6F1E395CCE5@sourceware.org \ --to=ibuclaw@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: linkBe 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).