similar to: [LLVMdev] use-diet design?

Hi Gabor, Could you give a little more detailed description of the plan with the user-diet changes? I read the README but still don't have a good picture of what will happen. Specifically, which operators new/delete will be overridden? What work will they do? How will the surrogate getters/setters work? Thanks, Dan

Hi Gabor, Thanks for posting the memory savings. 13% less memory usage in 447.dealII is very impressive. I haven't taken more than a very brief peek at this patch, but I have a few questions already. Is there a header missing? I don't see DECLARE_TRANSPARENT_OPERAND_ACCESSORS defined anywhere. Also, what affect does this macro have on doxygen? In User.h: +public: + template

On Apr 29, 2008, at 1:27 AM, Gabor Greif wrote: > 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. Hi

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 Apr 24, 2008, at 9:03 AM, Gabor Greif wrote: > > As you can see, the use-diet changes actually lower the build time > of kimwitu++! (this is as of yesterday's r50182). > Parity is not only reached, but surpassed. Thanks for these numbers. Do you know how much of this increase is due to co-allocating Use arrays with their users, and how much is due to the actual shrinking of

Hi all, in the last days I was busy gathering performance data about the "class Use"-related changes. I have nice measurements on a 8Gig MacPro with kimwitu++. This is important to say, because this machine is in plenty of memory, so swapping is not likely, which means that in more constrained setups (when swapping occurs) the use-diet approach is probably producing even better

Suppose, we have 3 people called: Francis, Cedric and Nina. Base on what they have eaten, we want to cluster people by "diet", "non-diet". # original data file, named as filename "food.csv". Francis|potato Francis|chocolate Francis|chocolate Francis|milk Cedric|vegetable Cedric|vegetable Cedric|potato Nina|potato Nina|chocolate Nina|chocolate Nina|potato # Step 1: I

Chris Lattner wrote: > Hi Gabor, I don't see OperandTraits.h. Sorry, I relied "svn diff" to include freshly added files. Apparently it did not :-/ Here are they. I pondered of putting all in Use.cpp into Value.cpp, but I am not so sure. Cheers, Gabor -------------- next part -------------- A non-text attachment was scrubbed... Name: OperandTraits.h Type:

On Apr 29, 2008, at 9:40 AM, Gabor Greif wrote: > Sorry, I relied "svn diff" to include freshly added files. svn add file svn diff . will show it.

Mike, Holger, thanks for the tips, but being a long-time subversion user, I already knew this all :-) The problem was that I did an SVN merge from branch to trunk, and I ended up with: ... M include/llvm/User.h A + include/llvm/OperandTraits.h M include/llvm/Instruction.h ... The little "+" after the "A" means, the file got copied unchanged, and I think this is

Hi all, here comes the patch for the first wave of Use class size reduction. I have split it into 3 files, corresponding to - header changes - implementation changes - applications This at the moment does not contain the description how the size of the Use class will be reduced from 16 to 12 bytes, I am going to send that in a separate patch. This wave primarily consists of changes that are

--- src/libFLAC/bitwriter.c | 31 +++++++++++++++---------------- 1 file changed, 15 insertions(+), 16 deletions(-) diff --git a/src/libFLAC/bitwriter.c b/src/libFLAC/bitwriter.c index 651440d..7da4b15 100644 --- a/src/libFLAC/bitwriter.c +++ b/src/libFLAC/bitwriter.c @@ -43,12 +43,11 @@ /* Things should be fastest when this matches the machine word size */ /* WATCHOUT: if you change this

On 2009-05-01, at 18:40, Stefanus Du Toit wrote: > Hi Nicolas, > > Looks like Preston and I have found the cause of the problem. The > issue is with PointerLikeTypeTraits<T*>::NumLowBitsAvailable. This > is set to 3, which basically assumes that unless the traits are > specialized for a particular pointer type, objects of that type are > allocated with malloc()

Hi Nicolas, Looks like Preston and I have found the cause of the problem. The issue is with PointerLikeTypeTraits<T*>::NumLowBitsAvailable. This is set to 3, which basically assumes that unless the traits are specialized for a particular pointer type, objects of that type are allocated with malloc() and aligned to 8 bytes. While PointerLikeTypeTraits is overloaded for Use*, it is

Hello everyone At EuroLLVM I presented some testing work we have been doing on improving correctness of the MC Layer for ARM. There seemed to be interest from the community in seeing the results of this test suite. Background ----------- We are using a test suite, called MC Hammer, that compares MC with an ARM in-house implementation of the same functionality. The test space for this suite is

You can call addIncoming(). /// addIncoming - Add an incoming value to the end of the PHI list /// void addIncoming(Value *V, BasicBlock *BB) { assert(V && "PHI node got a null value!"); assert(BB && "PHI node got a null basic block!"); assert(getType() == V->getType() && "All operands to PHI node must be the same

Closing this, found below links to get variable name.   http://groups.google.com/group/llvm-dev/browse_thread/thread/1a239f0d24db2b5c   http://markmail.org/message/fj5qg44vyjsdde7k#query:+page:1+mid:5zhmyncisenomcga+state:results           I could do following, to get the required information.                 const CallInst *CI = dyn_cast<CallInst>(Insn);                 int numoperands =

Otras variantes con y sin paquetes adicionales... > sapply(split(datIn$Gain, as.factor(datIn$Diet)), mean) d1 d2 d3 280 278 312 > by(datIn$Gain, datIn$Diet, mean) datIn$Diet: d1 [1] 280 -------------------------------------------------------------- datIn$Diet: d2 [1] 278 -------------------------------------------------------------- datIn$Diet: d3 [1] 312 > > library(dplyr) >

Hi, I'm having difficulty with getting a table to show with multiple rows and columns. Below is the commands that I've typed in and errors that I am getting. Thank you. Laura Table trying to enter: Diet: Binger-yes: Binger-No: Total: None 24 134 158 Healthy 9 52 61 Unhealthy 23 72 95 Dangerous 12 15 27 >

Me gusta la respuesta uqe has dado, pero si por ejemplo, alguno de los datos tiene datos faltantes, entonces devuelve NA. He probado con: sapply(split(datos$uno, as.factor(datos$dos)), mean(na.rm=TRUE)) pero da fallo. ¿Cómo se podría hacer para que devolviera además la media obviando los NA y que contara el numero de NA por categoria? > Date: Wed, 28 Oct 2015 00:13:45 +0100 > From: cof