<data name="EmittingPEFile" xml:space="preserve">
<value>Emitting R2R PE file: {0}</value>
</data>
+ <data name="MovingPEFile" xml:space="preserve">
+ <value>Moving R2R PE file: {0} to {1}</value>
+ </data>
<data name="EnableOptimizationsOption" xml:space="preserve">
<value>Enable optimizations</value>
</data>
<value>Method layout must be either DefaultSort or MethodOrder.</value>
</data>
<data name="InvalidMethodLayout" xml:space="preserve">
- <value>Method layout must be either DefaultSort, ExclusiveWeight, HotCold, HotWarmCold, or CallFrequency.</value>
+ <value>Method layout must be either DefaultSort, ExclusiveWeight, HotCold, HotWarmCold, CallFrequency, PettisHansen, or Random.</value>
</data>
<data name="CompileNoMethodsOption" xml:space="preserve">
<value>True to skip compiling methods into the R2R image (default = false)</value>
<value>Instruction set(s) to use for compilation</value>
</data>
<data name="InstructionSetMustNotBe" xml:space="preserve">
- <value>Instruction set must not be '{0}' for this architecture and operating system</value>
- </data>
- <data name="InstructionSetWithoutInputBubble" xml:space="preserve">
- <value>Instruction set(s) specified without also specifying input-bubble</value>
+ <value>Instruction set '{0}' is not valid for this architecture and operating system</value>
</data>
<data name="InstructionSetInvalidImplication" xml:space="preserve">
<value>Instruction set '{0}' implies support for instruction set '{1}'</value>
<data name="MissingOutputFile" xml:space="preserve">
<value>Output filename must be specified (--out <file>)</value>
</data>
+ <data name="MissingOutNearInput" xml:space="preserve">
+ <value>Single file compilation mode requires --out-near-input option</value>
+ </data>
<data name="InputWasNotLoadable" xml:space="preserve">
<value>No input files are loadable</value>
</data>
<data name="PerfMapFilePathOption" xml:space="preserve">
<value>Explicit specification of the PerfMap file path</value>
</data>
+ <data name="PerfMapFormatVersionOption" xml:space="preserve">
+ <value>Explicitly request a particular PerfMap format version</value>
+ </data>
+ <data name="OptionPassingHelp" xml:space="preserve">
+ <value>Options may be passed on the command line, or via response file. On the command line switch values may be specified by passing the option followed by a space followed by the value of the option, or by specifying a : between option and switch value. A response file is specified by passing the @ symbol before the response file name. In a response file all options must be specified on their own lines, and only the : syntax for switches is supported.</value>
+ </data>
+ <data name="DashDashHelp" xml:space="preserve">
+ <value>Use the '--' option to disambiguate between input files that have begin with -- and options. After a '--' option, all arguments are considered to be input files. If no input files begin with '--' then this option is not necessary.</value>
+ </data>
+ <data name="SwitchWithDefaultHelp" xml:space="preserve">
+ <value>Valid switches for {0} are: '{1}'. The default value is '{2}'.</value>
+ </data>
+ <data name="InstructionSetHelp" xml:space="preserve">
+ <value>The allowable values for the --instruction-set option are described in the table below. Each architecture has a different set of valid instruction sets, and multiple instruction sets may be specified by separating the instructions sets by a ','. For example 'avx2,bmi,lzcnt'</value>
+ </data>
+ <data name="MakeReproPathHelp" xml:space="preserve">
+ <value>Make a repro zip file in the specified path. This is used for sending error reports to the .NET team.</value>
+ </data>
</root>