From: Jan Hubicka <hubicka@ucw.cz>
To: gcc-patches@gcc.gnu.org, gerald@pfeifer.com
Subject: [wwwdocs] Add some more stuff into GCC14 changes.html
Date: Tue, 7 May 2024 12:34:57 +0200 [thread overview]
Message-ID: <ZjoD0U0M3l-gUjxX@kam.mff.cuni.cz> (raw)
Hi,
I realize that I am late for the release (sorry for that). But here are
few things which I think may be added to changes.html at least for those
who will look later.
OK?
Honza
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index ca5174de..b390db51 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -158,6 +158,22 @@ You may also want to check out our
or the vectorizer must be able to determine based on auxillary information
that the accesses are aligned.
</li>
+ <li>Significant improvements in maintenance of edge profile across
+ optimizations performing control flow changes.</li>
+ <li>Condition coverage instrumentation is now available using
+ <a href=https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-fcondition-coverage</a>-fcondition-coverage</a>
+ which can be analyzed using <code>gcov --conditions</code>.
+ <li>Inter-procedural value range propagation can now propagate value ranges
+ of return values of function and also ranges which can be derived from:
+ <pre>
+ if (val > constant)
+ __builtin_unreachable ();
+ </pre>
+ </li>
+ <li>Scalar replacement for aggregates now uses escape information
+ determined by mod-ref pass. This improves code generation in case
+ some C++ member functions are not inlined.</li>
+ </li>
</ul>
<!-- .................................................................. -->
<h2 id="languages">New Languages and Language specific improvements</h2>
@@ -582,6 +598,7 @@ You may also want to check out our
<li>Faster numeric conversions using <code>std::to_string</code> and
<code>std::to_wstring</code>.
</li>
+ <li>Significantly faster <code>std::vector::push_back</code>
<li>Updated parallel algorithms that are compatible with oneTBB.</li>
<li><code>std::numeric_limits<_Float32></code> and
<code>std::numeric_limits<_Float64></code> are now defined
reply other threads:[~2024-05-07 10:34 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=ZjoD0U0M3l-gUjxX@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).