Displaying 7 results from an estimated 7 matches for "emitcall".
Did you mean:
emitcall1
2014 Jan 20
2
[LLVMdev] Methods on addrspace pointers
...0x00000001030a4d1c llvm::IRBuilder<true, llvm::ConstantFolder, llvm::IRBuilderDefaultInserter<true> >::CreateCast(llvm::Instruction::CastOps, llvm::Value*, llvm::Type*, llvm::Twine const&) + 76
> 8 clang-3.4 0x0000000103bbeac3 clang::CodeGen::CodeGenFunction::EmitCall(clang::CodeGen::CGFunctionInfo const&, llvm::Value*, clang::CodeGen::ReturnValueSlot, clang::CodeGen::CallArgList const&, clang::Decl const*, llvm::Instruction**) + 3075
> 9 clang-3.4 0x0000000103c11c02 clang::CodeGen::CodeGenFunction::EmitCXXMemberCall(clang::CXXMethodDe...
2014 Oct 18
3
[LLVMdev] Performance regression on ARM
Hi Chandler,
That's embarrassing how weird this part of clang is. I have a provisional
patch which fixes the problem but underlines clang's problems. I will
submit it tonight for comments.
суббота, 18 октября 2014 г. пользователь Chandler Carruth написал:
>
> On Fri, Oct 17, 2014 at 7:51 AM, Anton Korobeynikov <
> anton at korobeynikov.info
>
2014 Jan 20
4
[LLVMdev] Methods on addrspace pointers
Thank you for the prompt response, Matt.
On Jan 20, 2014, at 3:03 PM, Matt Arsenault <Matthew.Arsenault at amd.com> wrote:
> Since 3.4 you need to use the addrspacecast instruction to cast between address spaces. It's possible there are still some places left that haven't been fixed yet to use it instead of creating bit casts.
Are you saying you think this is a bug and it should
2015 Jun 30
3
[LLVMdev] IC profiling infrastructure
...ctually
>>> generalizing the code.
>> In terms of value profiling code, there is no need for the check you
mentioned "if value kind is ..." at all, but 'attached' to the codegen
code for language construct of interests, for instance,
>> ... CodeGenFunction::EmitCall(...)
>> {
>> if (enable_indirect_profile) {
>> ....profileIndirectCall(); // does both instrumentation
>> and profile annotation depending on the context.
>> }
>> ...
>> }
>> Organizing the profile data according value profil...
2015 Jul 03
3
[LLVMdev] IC profiling infrastructure
...generalizing the code.
> >> In terms of value profiling code, there is no need for the check you
> mentioned "if value kind is ..." at all, but 'attached' to the codegen code
> for language construct of interests, for instance,
> >> ... CodeGenFunction::EmitCall(...)
> >> {
> >> if (enable_indirect_profile) {
> >> ....profileIndirectCall(); // does both instrumentation
> >> and profile annotation depending on the context.
> >> }
> >> ...
> >> }
> >> Organizing...
2015 Jun 29
3
[LLVMdev] IC profiling infrastructure
...re-done when we get to actually
> generalizing the code.
In terms of value profiling code, there is no need for the check you
mentioned "if value kind is ..." at all, but 'attached' to the codegen
code for language construct of interests, for instance,
... CodeGenFunction::EmitCall(...)
{
if (enable_indirect_profile) {
....profileIndirectCall(); // does both instrumentation
and profile annotation depending on the context.
}
...
}
Organizing the profile data according value profile kind allows
profile data to be independently loaded and used:
.. Co...
2015 Jun 22
4
[LLVMdev] IC profiling infrastructure
Justin, do you have more concerns on keeping value_kind?
If there is still disagreement, can we agree to move on with it for
now ? After the initial version of the patches checked in, we can do
more serious testings with large apps and revisit this if there are
problems discovered.
thanks,
David
On Mon, Jun 15, 2015 at 10:47 PM, Xinliang David Li <davidxl at google.com> wrote: