Am Tue, 5 Apr 2022 08:30:32 +0200
schrieb "Richard Biener" <richard.guent...@gmail.com>:
> If you have git write access you should add yourself in the DCO
> section in the MAINTAINERS file. Otherwise it has been said it's
> enough to explicitly state in mail that you are contributing this
> change under the Developer's Certificate of Origin Version 1.1
> (https://gcc.gnu.org/dco.html).
>
> Richard.
>
> >
> > Arno
Thank you all for your feedback and guidance. I have taken Eric's
feedback and deleted the relevant entry.
Since I do not have write access, I cannot add myself to the
MAINTAINERS file. Therefore, I want to explicitly state that I am
submitting these patches under the DCO. I have read and accept the
indications and requirements listed in (https://gcc.gnu.org/dco.html).
There are two patches, the original one, with the DCO signature at the
end and a second one, with the DCO signature too, with Eric's feedback.
Should anything else be required, do not hesitate to indicate so.
Signed-off-by: Fernando Oleo Blanco <irv...@irvise.xyz>
From a2f402895ab87713882adf2faef6f587d6d01264 Mon Sep 17 00:00:00 2001
From: Fernando Oleo Blanco <irv...@irvise.xyz>
Date: Mon, 4 Apr 2022 23:22:43 +0200
Subject: [PATCH 1/2] Add Ada's entry in the v12 changelog
---
htdocs/gcc-12/changes.html | 79 +++++++++++++++++++++++++++++++++++++-
1 file changed, 78 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 4e1f6b0f..16351697 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -183,7 +183,84 @@ a work-in-progress.</p>
</li>
</ul>
-<!-- <h3 id="ada">Ada</h3> -->
+<h3 id="ada">Ada</h3>
+<ul>
+ <li>Ada 2022
+ <ul>
+ <li>Added the <code>-gnat2022</code> flag to indicate strict Ada
+ 2022 compliance. The old <code>-gnat2020</code> flag is now
+ deprecated.</li>
+ <li>Support for Big Numbers (Annex G) has seen continuous
+ improvements. It is now cosidered complete. It is also proven to
+ be correct through the use of contracts and SPARK.</li>
+ <li>Continuous improvements to the Ada 2022 standard since GCC
+ 11. The main missing feature is support for the new
+ <code>parallel</code> keyword. However, some initial support has
+ already been put in place.</li>
+ <li>Greatly improved compile time support. More functions can now
+ have the <code>with Static</code> aspect and can be used in more
+ contexts.</li>
+ </ul>
+ </li>
+ <li>Ada 2022 extensions. The use of the <code>-gnatX</code> flag is
+ necessary to access these features as they are not considered
+ stable or standard.
+ <ul>
+ <li>Fixed lower bound for unconstrained arrays.
+ <ul>
+ <li><code>type Matrix is array (Natural range 0 .. <>, Natural
+ range 0 .. <>) of Integer;</code> is now valid.</li>
+ <li>Subtypes can also specify a lower bound: <code>subtype
+ String_1 is String (1 .. <>);</code>. Boundaries from slices
+ will "slide" to the correct lower bound of the subtype.</li>
+ </ul>
+ </li>
+ <li>Generalized <code>Object.Operand</code> notation. The follwing
+ code is now valid <code>V.Add_Element(42);</code>,
+ with <code>V</code> being a vector, for example.</li>
+ <li>Additional <code>when</code> constructs. Keywords
+ <code>return</code>, <code>goto</code> and <code>raise</code>
+ can now use <code>when</code> in addition to the existing
+ <code>exit when</code>. The following expression is therefore
+ now valid <code>raise Constraint_Error with "Element is null"
+ when Element = null;</code></li>
+ <li>Pattern matching</li>
+ <ul>
+ <li>The <code>case</code> statement has been extended to cover
+ records and arrays as well as finer grained casing on scalar
+ types. In the future it is expected to provide more compile
+ time guarantees when accessing discriminated fields. Case
+ exhaustion is supported for patter matching. An example would
+ be <code><pre>
+type Sign is (Neg, Zero, Pos);
+
+function Multiply (S1, S2 : Sign) return Sign is
+ (case (S1, S2) is
+ when (Neg, Neg) | (Pos, Pos) => Pos,
+ when (Zero, <>) | (<>, Zero) => Zero,
+ when (Neg, Pos) | (Pos, Neg) => Neg);
+ </pre></code></li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ <li><code>gnatfind</code> and <code>gnatxref</code>, which were
+ already deprecated, have been removed.</li>
+ <li>Support for <code>128bit</code> integers has beed added.</li>
+ <li>Greatly expanded code covered by contracts. Thanks to this work,
+ there are now several Ada standard libraries fully proven in SPARK
+ which means they have no runtime nor logical errors. They are
+ mostly numeric and string handling libraries.</li>
+ <li>Enable return-slot optimization for <code>Pure</code>
+ functions.</li>
+ <li>General optimizations, improvements and additions to the
+ standard library. Performance, correctness and in some cases
+ stability was improved. Memory pools have also seen some minor
+ enhancements.</li>
+ <li>Improvements to embedded-RTOS targets such as RTEMS, VxWorks and
+ QNX. Older targets were removed or cleaned.</li>
+ <li>Added some <a href="https://gcc.gnu.org/onlinedocs/gnat_rm/Security-Hardening-Features.html#Security-Hardening-Features";>hardening features</a>.</li>
+</ul>
<h3 id="c-family">C family</h3>
<ul>
--
2.35.1
Signed-off-by: Fernando Oleo Blanco <irv...@irvise.xyz>
From d9c1233cff4122b6cfa328688fb88646effc8cfa Mon Sep 17 00:00:00 2001
From: Fernando Oleo Blanco <irv...@irvise.xyz>
Date: Tue, 5 Apr 2022 18:32:45 +0200
Subject: [PATCH 2/2] Correct 128bit, it was added in GCC 11
---
htdocs/gcc-12/changes.html | 1 -
1 file changed, 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 16351697..d9b1e3ac 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -246,7 +246,6 @@ function Multiply (S1, S2 : Sign) return Sign is
</li>
<li><code>gnatfind</code> and <code>gnatxref</code>, which were
already deprecated, have been removed.</li>
- <li>Support for <code>128bit</code> integers has beed added.</li>
<li>Greatly expanded code covered by contracts. Thanks to this work,
there are now several Ada standard libraries fully proven in SPARK
which means they have no runtime nor logical errors. They are
--
2.35.1
Signed-off-by: Fernando Oleo Blanco <irv...@irvise.xyz>
