[llvm-bugs] [Bug 46323] New: Recommend -fprofile-generate instead of -fprofile-instr-generate for PGO in Clang's user manual

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=46323

            Bug ID: 46323
           Summary: Recommend -fprofile-generate instead of
                    -fprofile-instr-generate for PGO in Clang's user
                    manual
           Product: Documentation
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: General docs
          Assignee: unassignedbugs at nondot.org
          Reporter: hans at chromium.org
                CC: george.burgess.iv at gmail.com, llvm-bugs at lists.llvm.org,
                    xur at google.com

Clang's user manual currently recommends -fprofile-instr-generate for
instrumentation based profile-guided optimization
(https://clang.llvm.org/docs/UsersManual.html#profiling-with-instrumentation)

Towards the end of that section, there is a part about -fprofile-generate
saying it's an alternative instrumentation method.


However, my understanding is that -fprofile-generate is really better for PGO
(it supports value profiling for example), and -fprofile-instr-generate is best
left for code coverage analysis.

If my understand is correct, can we update the docs to reflect this?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200615/a70e4ba8/attachment.html>