Skip to content

Commit bbca881

Browse files
authored
Update details on data files
A user hit an issue when .pgc/.pgd files were kept at text in git. Turns out git was making changes to linefeed or CR type sequences for text and corrupted the file. User requested update of doc.
1 parent a32bd39 commit bbca881

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

‎docs/build/profile-guided-optimizations.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ To use profile-guided optimization, follow these steps to optimize your app:
3434
Your application can also directly invoke a PGO function, [PgoAutoSweep](pgoautosweep.md), to capture the profile data at the point of the call as a `.pgc` file. It can give you finer control over the code covered by the captured data in your `.pgc` files. For an example of how to use this function, see the [PgoAutoSweep](pgoautosweep.md) documentation.
3535

3636
When you create your instrumented build, by default, data collection is done in non-thread-safe mode, which is faster but may be imprecise. By using the **EXACT** argument to **/GENPROFILE** or **/FASTGENPROFILE**, you can specify data collection in thread-safe mode, which is more precise, but slower. This option is also available if you set the deprecated [PogoSafeMode](environment-variables-for-profile-guided-optimizations.md#pogosafemode) environment variable, or the deprecated **/POGOSAFEMODE** linker option, when you create your instrumented build.
37+
38+
Note: Both .pgc and .pgd files should be considered "binary" files if stored in a source control system to avoid any automatic transformation that may be made to "text" files.
3739

3840
- Link using **/LTCG** and **/USEPROFILE**.
3941

0 commit comments

Comments
 (0)