Displaying 7 results from an estimated 7 matches for "cpu_name".
2018 Mar 15
5
[RFC] llvm-exegesis: Automatic Measurement of Instruction Latency/Uops
...uilding the code snippets using instruction
descriptions from LLVM.
Results
-
Solving this bug <https://bugs.llvm.org/show_bug.cgi?id=36084>
(sandybridge):
> llvm-exegesis -opcode-name IMUL16rri8 -benchmark-mode latency
---
asm_template:
name: latency IMUL16rri8
cpu_name: sandybridge
llvm_triple: x86_64-grtev4-linux-gnu
num_repetitions: 10000
measurements:
- { key: latency, value: 4.0115, debug_string: '' }
error: ''
...
> llvm-exegesis -opcode-name IMUL16rri8 -benchmark-mode uops
---
asm_template:
name:...
2018 Mar 15
0
[RFC] llvm-exegesis: Automatic Measurement of Instruction Latency/Uops
...ults
>
> *
>
> Solving this bug
> <https://bugs.llvm.org/show_bug.cgi?id=36084>(sandybridge):
>
> > llvm-exegesis -opcode-name IMUL16rri8 -benchmark-mode latency
>
> ---
>
> asm_template:
>
> name: latency IMUL16rri8
>
> cpu_name: sandybridge
>
> llvm_triple: x86_64-grtev4-linux-gnu
>
> num_repetitions: 10000
>
> measurements:
>
> - { key: latency, value: 4.0115, debug_string: '' }
>
> error: ''
>
> ...
>
>
> > llvm-exegesis -opcode-na...
2018 Mar 15
3
[RFC] llvm-exegesis: Automatic Measurement of Instruction Latency/Uops
...Results
>
> -
>
> Solving this bug <https://bugs.llvm.org/show_bug.cgi?id=36084>
> (sandybridge):
>
> > llvm-exegesis -opcode-name IMUL16rri8 -benchmark-mode latency
>
> ---
>
> asm_template:
>
> name: latency IMUL16rri8
>
> cpu_name: sandybridge
>
> llvm_triple: x86_64-grtev4-linux-gnu
>
> num_repetitions: 10000
>
> measurements:
>
> - { key: latency, value: 4.0115, debug_string: '' }
>
> error: ''
>
> ...
>
> > llvm-exegesis -opcode-name IMUL16...
2018 Mar 15
0
[RFC] llvm-exegesis: Automatic Measurement of Instruction Latency/Uops
...Results
>
> *
>
> Solving this bug
> <https://bugs.llvm.org/show_bug.cgi?id=36084>(sandybridge):
>
> > llvm-exegesis -opcode-name IMUL16rri8 -benchmark-mode latency
>
> ---
>
> asm_template:
>
> name: latency IMUL16rri8
>
> cpu_name: sandybridge
>
> llvm_triple: x86_64-grtev4-linux-gnu
>
> num_repetitions: 10000
>
> measurements:
>
> - { key: latency, value: 4.0115, debug_string: '' }
>
> error: ''
>
> ...
>
>
> > llvm-exegesis -opcode-name I...
2019 Dec 17
2
[llvm-exegesis] Uops mode isnćt working
Hello,
I've been testing llvm-exegesis on X86. Latency and inverse_throughput modes work fine but when I run uops I get an error:
event not found - cannot create event uops_dispatched_port:port_0
LLVM ERROR: invalid perf event 'uops_dispatched_port:port_0'
I'm running this on a i7-4790K. Am I missing something on my computer or is this not yet fully implemented?
This also
2018 Mar 15
0
[RFC] llvm-exegesis: Automatic Measurement of Instruction Latency/Uops
...t;https://bugs.llvm.org/show_bug.cgi?id=36084>(sandybridge):
>>
>> > llvm-exegesis -opcode-name IMUL16rri8 -benchmark-mode latency
>>
>> ---
>>
>> asm_template:
>>
>> name: latency IMUL16rri8
>>
>> cpu_name: sandybridge
>>
>> llvm_triple: x86_64-grtev4-linux-gnu
>>
>> num_repetitions: 10000
>>
>> measurements:
>>
>> - { key: latency, value: 4.0115, debug_string: '' }
>>
>> error: ''...
2010 Nov 12
3
[LLVMdev] Build Attributes Proposal
...vm.attribute]
[%llvm.attribute { i32 1, i8* getelementptr inbounds ([3 x i8]* @.str,
i32 0, i32 0) }, %llvm.attribute zeroinitializer], align 4
@.str = private constant [3 x i8] c"O3\00"
And the target-specific has something like the CPU name and whether
it's using R9 as SB:
// 5 is CPU_name in ARM ABI, 14 is ABI_PCS_R9_use
@llvm.arm.attributes = appending global [2 x %llvm.attribute]
[%llvm.attribute { i32 5, i8* getelementptr inbounds ([10 x i8]*
@.str1, i32 0, i32 0) }, %llvm.attribute { i32 14, i8* null }], align
4
@.str1 = private constant [10 x i8] c"ARM946E-S\00"
Doc...