public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 0f12a937b22f2f94fc2d78e38bbec20bb4a0ee78
Date: Wed,  6 May 2020 09:07:07 +0000 (GMT)	[thread overview]
Message-ID: <20200506090707.7F4CF383F85E@sourceware.org> (raw)

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  0f12a937b22f2f94fc2d78e38bbec20bb4a0ee78 (commit)
      from  633c73cd5cb4d5997dedcf12002e64c79e8de46b (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 0f12a937b22f2f94fc2d78e38bbec20bb4a0ee78
Author: Jan Hubicka <hubicka@ucw.cz>
Date:   Wed May 6 11:06:46 2020 +0200

    Add symver and profile-base-prefix to changes.html.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index c1127c77..d1a7df0a 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -98,6 +98,12 @@ a work-in-progress.</p>
 	  This makes it possible to rebuild program
 	  with same outcome which is useful, for example, for distribution packages.
       </li>
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Optimize-Options.html#index-fprofile-prefix-path"><code>-fprofile-prefix-path</code></a>
+	  can be used in combination with <code>-fprofile-generate=profile_dir</code> and
+	  <code>-fprofile-use=profile_dir</code> to inform GCC where the base
+	  directory of build source tree is in case it differs between instrumentation
+	  and optimized builds.
+      </li>
       <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a>
 	enables a new static analysis pass and associated warnings.
 	This pass performs a time-consuming exploration of paths through
@@ -217,6 +223,12 @@ a work-in-progress.</p>
        the detection of invalid accesses by user-defined functions, such
        as those diagnosed by <code>-Wstringop-overflow</code>.
      </li>
+     <li>
+       The <code>symver</code> attribute can be used to bind symbols to
+       specific version nodes on ELF platforms. This is preferred to using
+       inline assembly with GNU as <code>symver</code> directive because the
+       latter is not compatible with link-time optimizations.
+     </li>
     </ul>
   </li>
   <li>New warnings:

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-10/changes.html | 12 ++++++++++++
 1 file changed, 12 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-05-06  9:07 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=20200506090707.7F4CF383F85E@sourceware.org \
    --to=hubicka@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: 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).