wwwdocs: Add symver and -fprofile-prefix-path to changes.html

wwwdocs: Add symver and -fprofile-prefix-path to changes.html

[Jan Hubicka]

Hi,
this patch adds mention of -fprofile-prefix-path and symver attribute.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 4497be14..45cb906f 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 is the base          
+	  directory of built source tree 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
@@ -207,6 +213,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> attributes can be used to to bind symbols to
+       specific version nodes on ELF platfroms. This is preferred to using
+       inline assembly with GAS <code>symver</code> directive because the later
+       is not compatible with link-time optimizations.
+     </li>
     </ul>
   </li>
   <li>New warnings:

Re: wwwdocs: Add symver and -fprofile-prefix-path to changes.html

[Gerald Pfeifer]

On Tue, 5 May 2020, Jan Hubicka wrote:
> this patch adds mention of -fprofile-prefix-path and symver attribute.

Thank you, Honza!

> +      <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 is the base          
> +	  directory of built source tree in case it differs between instrumentation
> +	  and optimized builds.

"...where the base directory ... is in case" (or "...resides in case")

Maybe "instrumented" instead of "instrumentation"?

And what is a "built source tree"?  Can we say "build tree"?

> +       The <code>symver</code> attributes can be used to to bind symbols to

"attribute" (singular) I believe?

"to to" -> "to"

> +       specific version nodes on ELF platfroms. This is preferred to using

"platforms"

> +       inline assembly with GAS <code>symver</code> directive because the later

"with the GNU as <code>symver</code> directive" (though "GNU as" over 
"GAS" is my preference, feel free to ignore).

"the latter"


Okay with those changes - thanks!

Gerald