Displaying 5 results from an estimated 5 matches for "aarch64instprint".
Did you mean:
aarch64instprinter
2018 Sep 26
5
RFC: Adding a code size analysis tool
...t. On the left hand side, you'll see the
demangled function name. The *change* in code size in bytes is reported on the
right hand side (only positive changes are reported).
clang::Sema::CheckHexagonBuiltinCpu([snip]) [function] 170316
ProcessDeclAttribute([snip]) [function] 125893
llvm::AArch64InstPrinter::printAliasInstr([snip]) [function] 105133
llvm::AArch64AppleInstPrinter::printAliasInstr([snip]) [function] 105133
ParseCodeGenArgs([snip]) [function] 64692
unswitchNontrivialInvariants([snip]) [function] 40180
getAttrKind([snip]) [function] 35811
clang::DumpCompilerOptionsAction::Exec...
2018 Oct 01
4
RFC: Adding a code size analysis tool
...#39;ll see the
> demangled function name. The *change* in code size in bytes is reported on the
> right hand side (only positive changes are reported).
>
> clang::Sema::CheckHexagonBuiltinCpu([snip]) [function] 170316
> ProcessDeclAttribute([snip]) [function] 125893
> llvm::AArch64InstPrinter::printAliasInstr([snip]) [function] 105133
> llvm::AArch64AppleInstPrinter::printAliasInstr([snip]) [function] 105133
> ParseCodeGenArgs([snip]) [function] 64692
> unswitchNontrivialInvariants([snip]) [function] 40180
> getAttrKind([snip]) [function] 35811
> clang::DumpCo...
2018 Oct 01
3
RFC: Adding a code size analysis tool
...demangled function name. The *change* in code size in bytes is reported on the
>> right hand side (only positive changes are reported).
>>
>> clang::Sema::CheckHexagonBuiltinCpu([snip]) [function] 170316
>> ProcessDeclAttribute([snip]) [function] 125893
>> llvm::AArch64InstPrinter::printAliasInstr([snip]) [function] 105133
>> llvm::AArch64AppleInstPrinter::printAliasInstr([snip]) [function] 105133
>> ParseCodeGenArgs([snip]) [function] 64692
>> unswitchNontrivialInvariants([snip]) [function] 40180
>> getAttrKind([snip]) [function] 35811
>...
2015 Mar 21
3
[LLVMdev] API Changes: TargetMachine::getSubtarget
Hi all,
As of r232885 I've removed the argument-less TargetMachine::getSubtarget
and TargetMachine::getSubtargetImpl. For the targets that aren't completely
independent of this I've gone ahead and left a non-virtual version of the
function in the target specific TargetMachine. What this means in practice
is that those targets can only use a bare getSubtarget call in their target
2014 Apr 03
5
[LLVMdev] comparing .o files from different build trees
...rget/AArch64/Release+Asserts/AArch64ISelDAGToDAG.o differ: byte 223462, line 2183
./lib/Target/AArch64/Release+Asserts/AArch64RegisterInfo.o ../../recurse2be/build/./lib/Target/AArch64/Release+Asserts/AArch64RegisterInfo.o differ: byte 20886, line 17
./lib/Target/AArch64/InstPrinter/Release+Asserts/AArch64InstPrinter.o ../../recurse2be/build/./lib/Target/AArch64/InstPrinter/Release+Asserts/AArch64InstPrinter.o differ: byte 332540, line 591
./lib/Target/AArch64/AsmParser/Release+Asserts/AArch64AsmParser.o ../../recurse2be/build/./lib/Target/AArch64/AsmParser/Release+Asserts/AArch64AsmParser.o differ: byte 2500...