On 04/03/2018 05:16 AM, Martin Liška wrote:
Hello.
I would like to document features I prepared in time frame of GCC 8.
Martin
Just a few minor nits:
@@ -113,6 +113,93 @@
possible for the user to have a finer-grained control over the loop
unrolling optimization.
</li>
+ <li>
+ GCOV tool can distinguish functions that begin on a same line in
Suggest either "The GCOV tool" (or perhaps preferably utility), or
just "GCOV."
+ <li>GCOV has more accurate numbers for execution of source line
executions.</li>
The duplication in "Number for executions of [...] executions"
reads a little awkward.
+ <li>Having a non-void function that does not return a value is
considered as
+ undefined behavior. The compiler considers such code as
unreachable and
+ makes more aggressive optimizations based on that.</li>
I think what we want to say might be something like:
A return statement without an operand in a non-void function
is considered unreachable and may be subject to optimization
on that basis.
It's not undefined to define such a function. What is undefined
is reaching that statement.
Martin
