public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@gdcproject.org>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] wwwdocs: Add D language changes and caveats to gcc-12/changes.html
Date: Wed, 17 Aug 2022 19:24:04 +0200	[thread overview]
Message-ID: <20220817172404.1025025-1-ibuclaw@gdcproject.org> (raw)

Hi,

This patch belatedly adds the new features and changes to the D
front-end during the GCC 12 development cycle, as well as a bullet in
the caveat section for D's new bootstrapping requirements.

If nothing stands out being really wrong, I'll go ahead and commit it by
end of week.

OK?

Regards,
Iain.

---
 htdocs/gcc-12/changes.html | 78 +++++++++++++++++++++++++++++++++++++-
 1 file changed, 77 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index ef957204..5bbad9bf 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -72,6 +72,17 @@ You may also want to check out our
     <code>pool</code> arguments. Those configurations had been broken for
     some time.
   </li>
+  <li>
+    <strong>D:</strong>
+    Building and bootstrapping GDC, the D compiler, now requires a working GDC
+    compiler (GCC version 9.1 or later) and D runtime library, libphobos, as
+    the D front end is written in D. On some targets, libphobos isn't enabled
+    by default, but compiles and works if <code>--enable-libphobos</code> is
+    used. Other targets may require a more recent minimum version of GCC to
+    bootstrap. Specifics are documented for affected targets in the
+    <a href="https://gcc.gnu.org/install/specific.html">manual</a> for
+    installing GCC.
+  </li>
   <li>
     <strong>Fortran:</strong>
     OpenMP code using the <code>omp_lib.h</code> include file can no longer be
@@ -509,7 +520,72 @@ function Multiply (S1, S2 : Sign) return Sign is
 </li>
 </ul>
 
-<!-- <h3 id="d">D</h3> -->
+<h3 id="d">D</h3>
+<ul>
+  <li>New features:
+    <ul>
+      <li>Support for the D programming language has been updated to version
+	2.100.1 of the language and run-time library. Full changelog for this
+	release and previous releases can be found on the
+	<a href="https://dlang.org/changelog/2.100.1.html">dlang.org</a>
+	website.
+      </li>
+      <li>On supported targets, the <code>__traits(compiles)</code> expression
+	can now be used to determine whether a target-specific built-in is
+	available without error during CTFE
+	(<a href="https://gcc.gnu.org/PR101127">PR101127</a>).
+      </li>
+      <li>Partial support for directly importing C99 sources into a D
+	compilation (<a href="https://dlang.org/spec/importc.html">ImportC</a>)
+	has been added to the language. A notable missing feature is support
+	for preprocessing C imports, which can be worked around by
+	preprocessing all C sources used for importing ahead of time.
+      </li>
+    </ul>
+  </li>
+  <li>New language options:
+    <ul>
+      <li><code>-fcheck=</code>, enables or disables the code generation of
+	specific run-time contract checks.
+      </li>
+      <li><code>-fcheckaction=</code>, controls the run-time behaviour on an
+	assert, array bounds check, or final switch contract failure. The
+	default is <code>-fcheckaction=throw</code>.
+      </li>
+      <li><code>-fdump-c++-spec=</code>, dumps all compiled
+	<code>extern(C++)</code> declarations as C++ code to a file.
+	The supplimentary option <code>-fdump-c++-spec-verbose</code> turns on
+	emission of comments for ignored declaration in the generated C++ spec.
+      </li>
+      <li><code>-fextern-std=</code>, controls which C++ standard
+	<code>extern(C++)</code> declarations are compiled to be compatible
+	with. The default is <code>-fextern-std=c++17</code>.
+      </li>
+      <li><code>-fpreview=</code>, added to enable upcoming D language features
+	in the compiler.
+      </li>
+      <li><code>-frevert=</code>, added to revert D language changes to support
+	older D codebases that need more time to transition.
+      </li>
+      <li><code>-fsave-mixins=</code>, saves mixins expanded at compile-time to
+	a file.
+      </li>
+    </ul>
+  </li>
+  <li>Deprecated and removed features:
+    <ul>
+      <li>The <code>-Wtemplates</code> compiler switch has been removed, as it
+	had been superceded by <code>-ftransition=templates</code>, which more
+	accurately reports on which templates have been instantiated.
+      </li>
+      <li>The <code>-ftransition=dip25</code> and
+	<code>-ftransition=dip1000</code> compiler switches have been renamed
+	to <code>-fpreview=dip25</code> and <code>-fprefix=dip1000</code>.
+      </li>
+    </ul>
+  </li>
+</ul>
+
 
 <h3 id="fortran">Fortran</h3>
 <ul>
-- 
2.34.1


             reply	other threads:[~2022-08-17 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 17:24 Iain Buclaw [this message]
2022-08-18  7:43 ` Richard Biener
2022-08-19 16:44 ` 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=20220817172404.1025025-1-ibuclaw@gdcproject.org \
    --to=ibuclaw@gdcproject.org \
    --cc=gcc-patches@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).