From: Andi Kleen <andi@firstfloor.org>
To: gcc-patches@gcc.gnu.org
Subject: [WEB][PATCH] Describe -pg and LTO changes
Date: Sun, 16 Nov 2014 20:54:00 -0000 [thread overview]
Message-ID: <20141116200245.GA10567@basil.fritz.box> (raw)
This patch describes some user visible changes that were
added to gcc 5.
Ok to commit?
-Andi
Index: htdocs/gcc-5/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
retrieving revision 1.25
diff -u -r1.25 changes.html
--- htdocs/gcc-5/changes.html 14 Nov 2014 21:32:32 -0000 1.25
+++ htdocs/gcc-5/changes.html 16 Nov 2014 20:03:07 -0000
@@ -154,6 +154,11 @@
about qualifiers on pointers being discarded via a new warning option
<code>-Wno-discarded-qualifiers</code>.</li>
<li>The C front end now generates more precise caret diagnostics.</li>
+ <li>The -pg option now only affects the current file in a LTO build.</li>
+ <li>A new no_reorder attribute has been added, that prevents reordering
+ of a specific symbol against other such symbols or inline assembler.
+ This is a more focussed alternative to
+ <code>-fno-toplevel-reorder</code>.
</ul>
<h3 id="cxx">C++</h3>
@@ -295,6 +300,17 @@
</ul>
+<h3 id="x86">IA-32/x86-64</h3>
+ <ul>
+ <li>The new <code>-mrecord-mcount</code> option for <code>-pg</code>
+ generates a Linux kernel style table of pointers to mcount or
+ __fentry__ calls at the beginning of functions. The new
+ <code>-mnop-mcount</code> option in addition also generates nops in
+ place of the __fentry__ or mcount call, so that a call per function
+ can be later patched in. This can be used for low overhead tracing or
+ hot code patching.</li>
+ </ul>
+
<h2 id="os">Operating Systems</h2>
<h3 id="dragonfly">DragonFly BSD</h3>
@@ -304,7 +320,11 @@
</ul>
<!-- h2>Documentation improvements</h2-->
-<!-- h2>Other significant improvements</h2 -->
-
+<h2>Other significant improvements</h2>
+ <h3 id="gcc-ar"></h3>
+ <ul>
+ <li>The <code>gcc-ar, gcc-nm, gcc-ranlib</code> wrappers now
+ understand a <code>-B</code> option to set the compiler to use.</li>
+ </ul>
</body>
</html>
next reply other threads:[~2014-11-16 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 20:54 Andi Kleen [this message]
2014-11-17 19:52 ` Jeff Law
2014-11-17 19:57 ` Jan Hubicka
2014-11-17 20:05 ` Jeff Law
2014-11-17 20:37 ` Andi Kleen
2015-04-08 16:41 ` 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=20141116200245.GA10567@basil.fritz.box \
--to=andi@firstfloor.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).