diff options
author | Kunal Pathak <Kunal.Pathak@microsoft.com> | 2021-06-10 03:42:14 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-06-10 03:42:14 +0300 |
commit | a4b3772d1ada339220145843138d4c622134adeb (patch) | |
tree | b4e58ae6692acbd9d7ae88d5d8f9617327ea47be /src/coreclr/ToolBox | |
parent | 327deea877581fbd73ae0de662152624a191645c (diff) |
Remove crossgen from superpmi tools (#53958)
* Remove crossgen SPMI collection
* Remove reference of crossgen from superpmi.py
* some misc crossgen references
* put back deleted things
Diffstat (limited to 'src/coreclr/ToolBox')
-rw-r--r-- | src/coreclr/ToolBox/superpmi/readme.md | 2 | ||||
-rw-r--r-- | src/coreclr/ToolBox/superpmi/superpmi-shim-collector/icorjitinfo.cpp | 2 | ||||
-rw-r--r-- | src/coreclr/ToolBox/superpmi/superpmi/icorjitinfo.cpp | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/src/coreclr/ToolBox/superpmi/readme.md b/src/coreclr/ToolBox/superpmi/readme.md index d9aded28c47..c3de3dfe942 100644 --- a/src/coreclr/ToolBox/superpmi/readme.md +++ b/src/coreclr/ToolBox/superpmi/readme.md @@ -91,7 +91,7 @@ speed up the disk operations. These are the general steps that are followed when doing a SuperPMI collection: 1. Collect .MC files. Set up for collection, then cause the JIT to be invoked -by either running a scenario, running tests, crossgen compiling assemblies, +by either running a scenario, running tests, crossgen2 compiling assemblies, or using PMI to force the JIT to compile functions in an assembly. During collection, the data for each JIT compiled function is stored in a uniquely named file with a ".MC" filename extension (for "method context"). diff --git a/src/coreclr/ToolBox/superpmi/superpmi-shim-collector/icorjitinfo.cpp b/src/coreclr/ToolBox/superpmi/superpmi-shim-collector/icorjitinfo.cpp index cd601a26213..de2c555c20a 100644 --- a/src/coreclr/ToolBox/superpmi/superpmi-shim-collector/icorjitinfo.cpp +++ b/src/coreclr/ToolBox/superpmi/superpmi-shim-collector/icorjitinfo.cpp @@ -2115,7 +2115,7 @@ uint16_t interceptor_ICJI::getRelocTypeHint(void* target) // For what machine does the VM expect the JIT to generate code? The VM // returns one of the IMAGE_FILE_MACHINE_* values. Note that if the VM -// is cross-compiling (such as the case for crossgen), it will return a +// is cross-compiling (such as the case for crossgen2), it will return a // different value than if it was compiling for the host architecture. // uint32_t interceptor_ICJI::getExpectedTargetArchitecture() diff --git a/src/coreclr/ToolBox/superpmi/superpmi/icorjitinfo.cpp b/src/coreclr/ToolBox/superpmi/superpmi/icorjitinfo.cpp index f1eb73b8915..91bf8bf2f77 100644 --- a/src/coreclr/ToolBox/superpmi/superpmi/icorjitinfo.cpp +++ b/src/coreclr/ToolBox/superpmi/superpmi/icorjitinfo.cpp @@ -1859,7 +1859,7 @@ uint16_t MyICJI::getRelocTypeHint(void* target) // For what machine does the VM expect the JIT to generate code? The VM // returns one of the IMAGE_FILE_MACHINE_* values. Note that if the VM -// is cross-compiling (such as the case for crossgen), it will return a +// is cross-compiling (such as the case for crossgen2), it will return a // different value than if it was compiling for the host architecture. // uint32_t MyICJI::getExpectedTargetArchitecture() |