search for: cgdecl

...tools/clang/lib/CodeGen/CGClass.cpp:1126:12: warning: parameter 'argBegin,argEnd' not found in the function declaration [-Wdocumentation] /// \param argBegin,argEnd the arguments to evaluate and pass to the ^~~~~~~~~~~~~~~ /home/grib/clang-scp/llvm/tools/clang/lib/CodeGen/CGDecl.cpp:1434:12: warning: parameter 'array' not found in the function declaration [-Wdocumentation] /// \param array - a value of type elementType* ^~~~~ /home/grib/clang-scp/llvm/tools/clang/lib/CodeGen/CGDecl.cpp:1435:12: warning: parameter 'destructionKind' not found...

...e following target specific modifications to clang and would like to get some advice from experts. 1) My target supports very poor stack access so we implement "static stack". In this model, all local variables will have static storage class. I think I can take care of this in the clang::CGDecl.cpp::CodeGenFunction::EmitBlockVarDecl() 2) To improve memory usage, I also would like to add a new default attribute "overlay" to local variables (all will have static storage class as mentioned in 1). This attribute will be applied to all local variables except if the user has explicit...

...perts. Ok. cfe-dev might be more appropriate for clang questions, but... > > 1) My target supports very poor stack access so we implement "static > stack". In this model, all local variables will have static storage > class. I think I can take care of this in the > clang::CGDecl.cpp::CodeGenFunction::EmitBlockVarDecl() Is there any reason not to lower these to alloca, and then have the code generator turn alloca into references to globals? That seems a more robust way to go. > 2) To improve memory usage, I also would like to add a new default > attribute &quot...

...perts. Ok. cfe-dev might be more appropriate for clang questions, but... > > 1) My target supports very poor stack access so we implement "static > stack". In this model, all local variables will have static storage > class. I think I can take care of this in the > clang::CGDecl.cpp::CodeGenFunction::EmitBlockVarDecl() Is there any reason not to lower these to alloca, and then have the code generator turn alloca into references to globals? That seems a more robust way to go. > 2) To improve memory usage, I also would like to add a new default > attribute &quot...

...e) at /home/athirumurthi/git/lldb/tools/clang/lib/CodeGen/CGExprScalar.cpp:3042 #32 0x00007ffff4b6b751 in clang::CodeGen::CodeGenFunction::EmitScalarInit (this=0x7fffffff9198, init=0xd6a5b0, D=0xd6a630, lvalue=..., capturedByInit=false) at /home/athirumurthi/git/lldb/tools/clang/lib/CodeGen/CGDecl.cpp:536 #33 0x00007ffff4b75d22 in EmitDeclInit (CGF=..., D=..., DeclPtr=0xd83068) at /home/athirumurthi/git/lldb/tools/clang/lib/CodeGen/CGDeclCXX.cpp:46 #34 0x00007ffff4b758c7 in clang::CodeGen::CodeGenFunction::EmitCXXGlobalVarDeclInit (this=0x7fffffff9198, D=..., DeclPtr=0xd83068, PerformInit=tr...

Hi John, I have looked into the EmitAutoVarAlloca() in CGDecl.cpp. However, I could not figure out how to employ my custom attribute for code generation. For example, my custom attribute is visible in CGDecl.cpp but how can I generate based on my custom attribute if (D.hasAttr<myCustomAttri>()) { //What to do here? } What I wan in IR is something l...

...e) at /home/athirumurthi/git/lldb/tools/clang/lib/CodeGen/CGExprScalar.cpp:3042 #32 0x00007ffff4b6b751 in clang::CodeGen::CodeGenFunction::EmitScalarInit (this=0x7fffffff9198, init=0xd6a5b0, D=0xd6a630, lvalue=..., capturedByInit=false) at /home/athirumurthi/git/lldb/tools/clang/lib/CodeGen/CGDecl.cpp:536 #33 0x00007ffff4b75d22 in EmitDeclInit (CGF=..., D=..., DeclPtr=0xd83068) at /home/athirumurthi/git/lldb/tools/clang/lib/CodeGen/CGDeclCXX.cpp:46 #34 0x00007ffff4b758c7 in clang::CodeGen::CodeGenFunction::EmitCXXGlobalVarDeclInit (this=0x7fffffff9198, D=..., DeclPtr=0xd83068, PerformInit=tr...

On Apr 10, 3:49 pm, Dominic Hamon <dom.ha... at gmail.com> wrote: > Hello Hi Dominic! > > I spent some time trying to get the test-suite running as per the > instructions here:http://www.llvm.org/docs/TestingGuide.html Yep. > > I was continually getting an error "No rule to make target > `Output/sse.expandfft.linked.rbc', needed by >

Hello I spent some time trying to get the test-suite running as per the instructions here: http://www.llvm.org/docs/TestingGuide.html I was continually getting an error "No rule to make target `Output/sse.expandfft.linked.rbc', needed by `Output/sse.expandfft.linked.bc'." Eventually, it turned out that calling configure without setting --with-llvmgccdir and having llvm-gcc

Hi Asit, thanks for the reply. But I guess I was not clear in my question. Actually, i dont want to use __ATTRIBUTE__((ANNOTATE("MOVIATTR"))), since in documentation it is stated that "This intrinsic allows annotation of local variables with arbitrary strings. This can be useful for special purpose optimizations that want to look for these annotations. These have no other