Used in profile-guided optimization to write all profile data from a running program to the .pgc file.

pgosweep [options] image pgcfile

options
(Optional) The valid values for options are:

• /? or /help displays the help message.

• /noreset preserves the count in the runtime data structures.

image
The full path of an .exe or .dll file that was created by using the /GENPROFILE, /FASTGENPROFILE, or /LTCG:PGINSTRUMENT option.

pgcfile
The .pgc file where this command writes out the data counts.

The pgosweep command works on programs that were built by using the /GENPROFILE or /FASTGENPROFILE option, or the deprecated /LTCG:PGINSTRUMENT option. It interrupts a running program and writes the profile data to a new .pgc file. By default, the command resets counts after each write operation. If you specify the /noreset option, the command will record the values, but not reset them in the running program. This option gives you duplicate data if you retrieve the profile data later.

An alternative use for pgosweep is to retrieve profile information just for the normal operation of the application. For example, you could run pgosweep shortly after you start the application and discard that file. This would remove profile data associated with startup costs. Then, you can run pgosweep before ending the application. Now the collected data has profile information only from the time the user could interact with the program.

When you name a .pgc file (by using the pgcfile parameter) you can use the standard format, which is appname!n.pgc. If you use this format, the compiler automatically finds this data in the /LTCG /USEPROFILE or /LTCG:PGO phase. If you do not use the standard format, you must use pgomgr to merge the .pgc files.

For information on how to capture the profile data from within your executable, see PgoAutoSweep.

In this example command, pgosweep writes the current profile information for myapp.exe to myapp!1.pgc.

pgosweep myapp.exe myapp!1.pgc

Profile-Guided Optimizations
PgoAutoSweep