search for: mduser

...quote some numbers for memory savings below >> based on an -flto -g bootstrap of `llvm-lto` (i.e., running `llvm-lto` >> on `llvm-lto.lto.bc`, an already-linked bitcode file dumped by ld64's >> -save-temps option) that currently peaks at 15.3GB. >> >> 1. Introduce `MDUser`, which inherits from `User`, and whose `Use`s >> must all be metadata. The cost per operand is 1 pointer, vs. 4 >> pointers in an `MDNode`. >> >> 2. Create `MDLineTable` as the first subclass of `MDUser`. Use normal >> fields (not `Value`s) for the line and...

...ase RAUW speed. My rough plan follows. I quote some numbers for memory savings below based on an -flto -g bootstrap of `llvm-lto` (i.e., running `llvm-lto` on `llvm-lto.lto.bc`, an already-linked bitcode file dumped by ld64's -save-temps option) that currently peaks at 15.3GB. 1. Introduce `MDUser`, which inherits from `User`, and whose `Use`s must all be metadata. The cost per operand is 1 pointer, vs. 4 pointers in an `MDNode`. 2. Create `MDLineTable` as the first subclass of `MDUser`. Use normal fields (not `Value`s) for the line and column, and use `Use` operands for...

...of debug info we use, and changing their schema, ownership, and uniquing along the way. I'm not going to touch any other metadata, although certainly if we find that (e.g.) profile metadata has become a source of pain, we could customize it in the future. > I also think the relationship of MDUser, MDNode, and MDString need to be clarified a great deal. Why doesn't getMetadata return an 'MDUser*' for example? In the class hierarchy: - Value -> MDString - Value -> MDNode - Value -> NamedMDNode - Value -> User -> MDUser -> ... I named `MDUser` by its re...

...m "process monitor" in real time. -- Sean Silva > > -eric > > > > > Also, you seem to really like saying "peak" here. Is there a definite > peak? > > When does it occur? > > > > > >> > >> > >> 1. Introduce `MDUser`, which inherits from `User`, and whose `Use`s > >> must all be metadata. The cost per operand is 1 pointer, vs. 4 > >> pointers in an `MDNode`. > >> > >> 2. Create `MDLineTable` as the first subclass of `MDUser`. Use normal > >> fields (n...

...issue I was seeing last Summer is still there, you should see that the invocation of llvm-link is actually the most memory-intensive part of the LTO step, by far. Also, you seem to really like saying "peak" here. Is there a definite peak? When does it occur? > > 1. Introduce `MDUser`, which inherits from `User`, and whose `Use`s > must all be metadata. The cost per operand is 1 pointer, vs. 4 > pointers in an `MDNode`. > > 2. Create `MDLineTable` as the first subclass of `MDUser`. Use normal > fields (not `Value`s) for the line and column, and use...

...to commit the API changes incrementally so we can fix any issues there before pushing the functionality changes. Unfortunately, this currently adds a lot of noise to the (squashed) patch. Introducing `MDLocation` ======================== Of course, this adds `MDLocation`, the first subclass of `MDUser`. This is a first-class IR type that has two other representations: `DILocation` (which now trivially wraps `MDLocation` instead of `MDNode`) and `DebugLoc`. I've genericised the code in `LLParser` (and elsewhere) to sketch out how adding other `MDUser` subclasses will go. Perhaps I used the...

...guration is, R Ver-2.12 Package Installed : RODBC_1.3-2 - here iam trying to install (RODBC_1.3-6) which will support for R 2.12. But getting error while do installation. ================================ERROR I GETTING====================================================== C:\Documents and Settings\mduser>R CMD INSTALL "C:\Program Files\R\R-2.12.0\bin\ RODBC_1.3-6.tar.gz" * installing to library 'C:/PROGRA~1/R/R-212~1.0/library' * installing *source* package 'RODBC' ... ** libs gcc -I"C:/PROGRA~1/R/R-212~1.0/include" -I. -O3 -Wall -std=gnu99 -c RODB C.c...

...gt;> 7. (Optional) Refactor `DebugMDNode` sub-classes to minimize RAUW >> traffic during bitcode serialization. Now that metadata types are >> known, we can write debug info out in an order that makes it cheap >> to read back in. >> >> Note that using `MDUser` will make RAUW much cheaper, since we're >> using the use-list infrastructure for most of them. If RAUW isn't >> showing up in a profile, I may skip this. > On 2014 Oct 18, at 10:27, Sean Silva <chisophugis at gmail.com> wrote: > >> Since debug info...

> On Oct 17, 2014, at 3:54 PM, Sean Silva <chisophugis at gmail.com> wrote: > > this seems like the classic situation where the someone comes to you asking for X, but what they really want is a solution to underlying problem Y, for which the best solution, once you actually analyze Y, is Z. On the contrary, I came into this expecting to work with Eric on parallelizing the backend,