similar to: [LLVMdev] splice problem

Hi all, I have a problem with passing multiple option(-flag=aaa/bbb) from clang to llvm, I don't know how to parse it, should I parse it in clang and pass it to llvm or should I parse it in llvm pass where I use it, could you help me. Thanks in advance, Sevak.

Hi all, As part of my bachelor's thesis I'm trying to implement a new LLVM-based back end for the OCaml compiler. Currently I have a problem with LLVM's interface to the OCaml garbage collector. When I try to compile the attached program using llc I get the following stack dump: 0 llc 0x00000000016611de 1 llc 0x00000000016616aa 2 libpthread.so.0

On 2007-09-03, at 23:14, Talin wrote: > On Sep 2, 2007 5:31 AM, Gordon Henriksen <gordonhenriksen at mac.com> > wrote: > >> On Sep 2, 2007, at 04:54, Talin wrote: >> >>> I've been looking through the documentation (http://llvm.org/docs/ >>> GarbageCollection.html) on how to implement a garbage collector >>> for LLVM and there's a

Hi, I have trouble making my ProfileInfo-Analysis available in the backend, I have changed llc so it loads the ProfileInfo if requested, the PassManger gives this output: > Target Data Layout > Create Garbage Collector Module Metadata > Basic Alias Analysis (default AA impl) > DWARF Information Writer > No Profile Information > Module Information > ModulePass

Hi all, As part of my bachelor's thesis I'm trying to implement a new LLVM-based back end for the OCaml compiler. Currently I have a problem with LLVM's interface to the OCaml garbage collector. When I try to compile the attached program using llc I get the following stack dump: 0 llc 0x00000000016611de 1 llc 0x00000000016616aa 2 libpthread.so.0

Gordon Henriksen wrote: > The intrinsics are entirely neutral to collector implementation, and > thus to threading. They could easily be used to implement reference > counting, for instance, which may or may not be implemented in a > threadsafe manner. However, as with your algorithm, reference counting > does not require code generator support, and so would not justify the

Thanks for the example code. Its gives a good idea how the shadow stack works. But I have another question. Using the shadow stack is a nice and simple way to implement GC, but it might have a large runtime overhead per function call. Is there another way to preserve garbage specific information (gcroots) through the llvm optimizer and native code generator? This information could be used to

On 2/22/2012 7:29 AM, Sevak Sargsyan wrote: > Hi all, > I have problem with debugging clang, gdb does not stop in function > ParseFrontendArgs, the function works because I wrote errs() and I saw > it in command line, > I also wrote __asm__("int $3") in ParseFrontendArgs but it does not help. Are you debugging the correct process? Note that invocations of

This is a template that takes care of managing plugin registries. I wrote it because I got the distinct feeling I was needlessly reinventing the wheel as I wrote a collector registry. I haven't converted anything else to use it, though. Still, it's orthogonal and has become stable in my usage, so I thought I'd submit it in advance. To get my collector registry going, all I

Hi Jan, In the lisp code you provide the operators are parsed as simple symbols in a pairlist. In the R snippet, they are parsed as left-associative binary operators of equal precedence. If you unquote a call in the right-hand side, you're artificially bypassing the left-associativity of these operators. To achieve what you're looking for in a general way, you'll need a more precise

Hello, I've meanwhile got onechannelGUI running (my OS is windows). I'm trying to use it for the analysis of human exon arrays. I was able to load cel files and run them through affymetrix power tools, to obtain normalized affy data. My next step was trying to find differentially spliced exons. The menu offers to calculate either Midas or splice index scores. However, when I try to use

> What does "llc -debug-pass=Structure" say? Is the ProfileLoaderPass > really the last pass to touch the ProfileInfo before you are using it? Below is the sequence of passes that I see. Although the NoProfileInfo pass is being run, it should be subsequently overridden by ProfileInfoLoaderPass (LoaderPass) correct? Target Data Layout Create Garbage Collector Module Metadata

On 2009-02-26 18:22, Gabor Greif wrote: > On Feb 26, 2:18 pm, Ralf Schneider <li... at gestaltgeber.com> wrote: > >> Hello, >> >> 2009/2/26 Talin <viri... at gmail.com> >> >> >>> The IR-level intrinsics themselves don't much help you *write* a GC, so >>> much as to integrate one with LLVM. What is provided is essentially

Shuguang Feng wrote: >> What does "llc -debug-pass=Structure" say? Is the ProfileLoaderPass >> really the last pass to touch the ProfileInfo before you are using it? > > Below is the sequence of passes that I see. Although the > NoProfileInfo pass is being run, it should be subsequently overridden > by ProfileInfoLoaderPass (LoaderPass) correct? Yes. >

Hi, I often need to take columns from two data.frames and 'splice' them together (alternately taking a column from the first data frame, then from the second). For example: x <- table(sample(letters[1:9], 100, replace=TRUE), sample(letters[1:4], 100, replace=TRUE)) y <- prop.table(x) splice <- function (x, y) { z <- matrix(rep(NA, (ncol(x) * 2) * nrow(x)), nrow

Sorry, I meant to say, I added code to prevent llc from running machine verifier after delay slots are filled. MipsInstrInfo::AnalyzeBranch generates incorrect results after delay slots are filled. Also, it seems that code in MachineVerifier.cpp wasn't written with architectures that have delay slots in mind. On Wed, Apr 25, 2012 at 11:59 AM, Akira Hatanaka <ahatanak at gmail.com>

On Feb 26, 2:18 pm, Ralf Schneider <li... at gestaltgeber.com> wrote: > Hello, > > 2009/2/26 Talin <viri... at gmail.com> > > > The IR-level intrinsics themselves don't much help you *write* a GC, so > > much as to integrate one with LLVM. What is provided is essentially a > > mechanism for walking the stack, and a means to insert read/write > >

Compile out splice support from virtio character driver when the splice-family of syscalls is not supported by the system (i.e. CONFIG_SYSCALL_SPLICE is undefined). Signed-off-by: Pieter Smith <pieter at boesman.nl> --- drivers/char/virtio_console.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c index

Compile out splice support from virtio character driver when the splice-family of syscalls is not supported by the system (i.e. CONFIG_SYSCALL_SPLICE is undefined). Signed-off-by: Pieter Smith <pieter at boesman.nl> --- drivers/char/virtio_console.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c index

Hi Anton, I ran llc with -verify-coalescing. There were no error messages. Then I added code in MipsPassConfig::addPreEmitPass() to prevent machine verifier from running post delay -slot-filler, and ran llc again. Again, there were no error messages. This is the list of passes run after post-RA scheduling. machine verifier is run twice after post RA scheduler (and CriticalAntiDepBreaker) is run.