search for: parameterattribut

With trunk(r56943), I get: make[3]: Entering directory `/home/tinuviel/llvm/vmkit/lib/JnJVM/VMCore' llvm[3]: Compiling JnjvmModule.cpp for Debug build JnjvmModule.cpp:11:38: error: llvm/ParameterAttributes.h: No such file or directory -- Seo Sanghyeon

...in A0", but can I custom lower to that immediately given that > I'm going to do a tapdance with the instruction selections later on? > If not, how do I distinguish these arguments from the data argument > later on? Hrm. I suspect you'll have to add parameter attribute (see ParameterAttributes.h) that indicates it's used as an address. In SelectionDAGIsel.cpp:TargetLowering::LowerAguments(), you have access to the function argument type. Anyone sees an alternative solution? Evan > > Thanks, > Andreas > _______________________________________________ > LLVM Deve...

...tagThree }; Why such a generic pointer tagging mechanism? This should either be specific to the application or in a shared location (e.g. include/llvm/ Support). +++ include/llvm/Instructions.h (Arbeitskopie) @@ -21,10 +21,10 @@ #include "llvm/DerivedTypes.h" #include "llvm/ParameterAttributes.h" +#include "llvm/BasicBlock.h" Why the #include? Please avoid this if possible. Why are operand lists stored as templates instead of arrays? "Op<0>" is very strange to me. /// Constructors - These two constructors are convenience methods because one...

On 10/1/07, Evan Cheng <evan.cheng at apple.com> wrote: > > If I lower the calling convention stuff manually rather than relying > > on the generated CC analyzer, how do I determine that a formal > > argument I'm about to receive or pack together is supposed to be used > > as a pointer so I can stick it in an address register? > > I'd suggest custom

The ARM EABI (AAPCS) defines: - i64 values are 8-bytes aligned - "The alignment of an aggregate shall be the alignment of its most-aligned component." So, struct ss { int x; int y; }; void f(int a, struct ss b); r0 <- a r1-r2 <- b void g(int a, long long b); r0 <- a r2-r3 <- b The problem is: llvm-gcc generates the same bytecode for both functions: declare void

Hi all, I have reported more than enough about the space savings achieved and the associated costs, here comes the current patch for review. Since this one is substantially smaller than the previous one, I did not cut it in pieces. The front part is about headers and the rest the .cpp and other files. Cheers, Gabor -------------- next part -------------- An embedded and charset-unspecified

On Sep 29, 2007, at 2:57 PM, Andreas Fredriksson <deplinenoise at gmail.com> wrote: > On 9/25/07, Evan Cheng <evan.cheng at apple.com> wrote: >>> Hi Evan, >>> wouldn't this generate fairly terrible code if each address register >>> use has to be preceded by instructions to make an address register >>> hold the right value? >> >>

..., from /home/edd/llvm/llvm-2.3/include/llvm/Module.h:17, from /home/edd/llvm/llvm-2.3/include/llvm-c/Core.h:40, from /home/edd/llvm/llvm-2.3/include/llvm-c/BitWriter.h:22, from BitWriter.cpp:10: /home/edd/llvm/llvm-2.3/include/llvm/ParameterAttributes.h:71: warning: `inline ' is not at beginning of declaration BitWriter.cpp: In function `int LLVMWriteBitcodeToFileHandle(LLVMOpaqueModule*, int)': BitWriter.cpp:40: error: no matching function for call to ` __gnu_cxx::stdio_filebuf<char, std::char_traits<char> >::stdi...