Displaying 3 results from an estimated 3 matches for "hardwareunit".
Did you mean:
hardwareunits
2020 May 10
2
[llvm-mca] Resource consumption of ProcResGroups
...-mtriple=x86_64-unknown-unknown
> -march=x86-64 -mcpu=haswell`
> crashes (because fxrstor requests
> `HWPort0,HWPort6,HWPort23,HWPort05,HWPort06,HWPort15,HWPort0156`, so
> HWPort0156 ends up asserting because 0,1,5, and 6 are all taken), so I
> added:
> ```
> --- a/llvm/lib/MCA/HardwareUnits/ResourceManager.cpp
> +++ b/llvm/lib/MCA/HardwareUnits/ResourceManager.cpp
> @@ -292,7 +292,7 @@ void ResourceManager::issueInstruction(
> ResourceState &RS = *Resources[Index];
>
> - if (!R.second.isReserved()) {
> + if (!R.second.isReserved() && RS.isReady()) {
>...
2020 May 10
2
[llvm-mca] Resource consumption of ProcResGroups
> On May 9, 2020, at 5:12 PM, Andrea Di Biagio via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> The llvm scheduling model is quite simple and doesn't allow mca to accurately simulate the execution of individual uOPs. That limitation is sort-of acceptable if you consider how the scheduling model framework was originally designed with a different goal in mind (i.e. machine
2019 Apr 30
6
Disk space and RAM requirements in docs
...t/X86/InstPrinter
3.4M build/lib/Target/NVPTX/MCTargetDesc/CMakeFiles/LLVMNVPTXDesc.dir
3.4M build/lib/Target/NVPTX/MCTargetDesc/CMakeFiles
3.4M build/lib/Target/NVPTX/MCTargetDesc
3.3M build/lib/MC/MCDisassembler/CMakeFiles
3.3M build/lib/MC/MCDisassembler
3.2M build/lib/MCA/CMakeFiles/LLVMMCA.dir/HardwareUnits
3.2M build/lib/MC/MCDisassembler/CMakeFiles/LLVMMCDisassembler.dir
3.2M build/lib/DebugInfo/MSF/CMakeFiles/LLVMDebugInfoMSF.dir
3.2M build/lib/DebugInfo/MSF/CMakeFiles
3.2M build/lib/DebugInfo/MSF
3.1M build/tools/llvm-cat/CMakeFiles/llvm-cat.dir
3.1M build/tools/llvm-cat/CMakeFiles
3.1M build/too...