On 10/26/2017 01:21 AM, Martin Liška wrote:
On 10/20/2017 06:03 AM, Sandra Loosemore wrote:
On 10/19/2017 12:26 PM, Eric Gallager wrote:
On 10/19/17, Martin Liška <mli...@suse.cz> wrote:
Hi.
As discussed in the PR, we should be more precise in our documentation.
The patch does that.
Ready for trunk?
Martin
gcc/ChangeLog:
2017-10-19 Martin Liska <mli...@suse.cz>
PR gcov-profile/82457
* doc/invoke.texi: Document that one needs a non-strict ISO mode
for fork-like functions to be properly instrumented.
---
gcc/doc/invoke.texi | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
The wording is kinda unclear because the modes in the parentheses are
all strict ISO modes, but the part before the parentheses says
NON-strict... I think you either need an additional "not" inside the
parentheses, or to change all the instances of -std=c* to -std=gnu*.
The wording in the patch doesn't make sense to me, either. If I understand the
issue correctly, the intent is probably to say something like
Unless a strict ISO C dialect option is in effect,
@code{fork} calls are detected and correctly handled without double counting.
??
Hi Sandra.
Thank you for the feedback, I'm sending version you suggested. Hope it's fine
to install the patch?
Ummm, no. Sorry to have been unclear; the wording I suggested above was
intended to replace the existing sentence about fork behavior, not to be
appended to it.
-Sandra
