search for: sampleprofile

On Mar 13, 2014, at 5:48 AM, Diego Novillo <dnovillo at google.com> wrote: > On Wed, Mar 12, 2014 at 9:09 PM, Justin Bogner <mail at justinbogner.com> wrote: > >> Functions are represented by strings, determined by the part of the >> frontend that both generates and uses this data. In our case, these are >> generally whatever clang thinks of as the

> On 10/24/2014 05:26 PM, betulb at codeaurora.org wrote: >> Hi All, >> >> We've been working on enhancing LLVM's instrumentation based profiling >> by >> adding indirect call target profiling support. Our goal is to add >> instrumentation around indirect call sites, so that we may track the >> frequently taken target addresses and their call

The frontend-driven instrumentation based profiling used for clang's -fprofile-instr-generate and -fprofile-instr-use currently has logic for handling its data format spread about a few different places: 1. Reading files is done in clang when -fprofile-instr-use is specified. The logic is in CodeGen/CodeGenPGO.cpp. 2. Reading files is done by the (very preliminary) llvm-profdata tool,

...s a proposal for the instrumentation-based approach that I talked about at the dev meeting. I don’t see how it can share the a file format with the sample profiler, since the content is fundamentally different. > > I think we should be able to use the same pass in > lib/Transforms/Scalar/SampleProfile.cpp to read profiles generated > from instrumentation. The information is basically the same, so a bit > of generalization of that code should be all we need to pass those > counters down into the analysis module. ?? The information is completely different.

...MCJIT' llvm[4]: Compiling X86MachORelocationInfo.cpp for Release+Asserts build llvm[3]: Compiling MCJIT.cpp for Release+Asserts build llvm[2]: Compiling BasicTargetTransformInfo.cpp for Release+Asserts build llvm[4]: Compiling X86MachObjectWriter.cpp for Release+Asserts build llvm[3]: Compiling SampleProfile.cpp for Release+Asserts build llvm[3]: Building Release+Asserts Archive Library libLLVMMCJIT.a make[3]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/lib/ExecutionEngine/MCJIT' make[3]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/lib/ExecutionEngine/Orc' llvm[3]: Compil...