search for: felixcca

...vailable URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150521/31abf2d3/attachment.obj> -------------- next part -------------- > Le 2015-05-21 à 14:53:44, Daniel Berlin <dberlin at dberlin.org> a écrit : > > On Thu, May 21, 2015 at 11:37 AM, Félix Cloutier <felixcca at yahoo.ca> wrote: >> Hi all, >> >> I have a custom alias analysis pass that enforces that pointers from different address spaces do not alias, and I'm using MemoryDependenceAnalysis to, well, figure out dependence analysis. >> >> The AA pass is extremely sim...

...an do something similar to PCH to parse the fragment in context of all of the headers. I don't know much about feeding clang buffers instead of files, but I believe it can be done with some of the "virtual" file suport that has been added recently. Reid 2011/2/21 Félix Cloutier <felixcca at yahoo.ca>: > Hello guys, > > I'd like to use Clang to parse snippets of (and emit bytecode for) C++ code that come from larger files that don't contain only C++, but looking at the clang interpreter example, either I didn't get it, or it looks like the driver expects only...

...ased. Most Linux distributions have picked this up, so it should Just Work on Linux. Apple's GDB is stale (6.3 + lots of patches). They've stopped updating the version of GDB they ship with XCode, and now they're spending their time working on LLDB. Reid 2010/7/4 Félix Cloutier <felixcca at yahoo.ca>: > Hey guys, > > I'd need to debug just-in-time compiled code under Mac OS. As predicted, GDB doesn't cope really well with it. The LLVM manual seems to say it's possible to patch GDB under Linux, but there seems to be no option for Mac OS. > > What can I...

Hey guys, I'd need to debug just-in-time compiled code under Mac OS. As predicted, GDB doesn't cope really well with it. The LLVM manual seems to say it's possible to patch GDB under Linux, but there seems to be no option for Mac OS. What can I do? I'd prefer a solution that integrates with Xcode, but I'll manage if it doesn't and I have to run the debugger externally.

Hello everyone, I've been watching LLVM since about a year now, and I thought it was finally time I'd do something with it. So I've got my hands dirty with a cool project (who knows? maybe I'll end up releasing it), but since I'm fairly new to the whole thing, there are still a number of things I'm not too sure about. First, the way we create instructions confuses me a

2010/6/24 Félix Cloutier <felixcca at yahoo.ca>: > Hello everyone, > > I've been watching LLVM since about a year now, and I thought it was finally time I'd do something with it. So I've got my hands dirty with a cool project (who knows? maybe I'll end up releasing it), but since I'm fairly new to the...

Hi all, I have a custom alias analysis pass that enforces that pointers from different address spaces do not alias, and I'm using MemoryDependenceAnalysis to, well, figure out dependence analysis. The AA pass is extremely simple, it only checks the address space of pointers, returns NoAlias if they're different, and delegates otherwise. It is the last alias analysis pass added to my

Hello guys, I'd like to use Clang to parse snippets of (and emit bytecode for) C++ code that come from larger files that don't contain only C++, but looking at the clang interpreter example, either I didn't get it, or it looks like the driver expects only files, and not strings or char buffers. Is there a simple way to achieve this? Do I have to split my input into small files and

So I got very mixed results. With the CallGraphSCCPass, both `addRequired<DominatorTreeWrapperPass>` and `addRequired<MemoryDependenceAnalysis>` fail at runtime. The LLVM core has just two CallGraphSCCPasses and neither uses neither analyses, so it's hard to find a valid example. I transformed the pass into a ModulePass, using scc_iterator as shown in CGPassManager to process

...e application wants to generate code, which for some people may not be that often. This is a new model that doesn't really fit with the current interface, but it could be made to work. I just wanted to throw the idea out for discussion and to gauge interest. Reid 2010/7/7 Félix Cloutier <felixcca at yahoo.ca>: > Wouldn't it mean each time a function is compiled it would need to be bundled to its own dylib? How well would that scale? > > Félix > > Le 2010-07-07 à 15:41:18, Reid Kleckner a écrit : > >> On Tue, Jul 6, 2010 at 9:08 AM, Greg Clayton <gclayton at...

Wouldn't it mean each time a function is compiled it would need to be bundled to its own dylib? How well would that scale? Félix Le 2010-07-07 à 15:41:18, Reid Kleckner a écrit : > On Tue, Jul 6, 2010 at 9:08 AM, Greg Clayton <gclayton at apple.com> wrote: >>> 2) Can I easily debug JIT'd code with LLDB? >> >> Are you running JIT'd code within another

...eate it using the very handy: /usr/local/bin/llc -march=cpp source.s which creates a file called source.s.cpp which contains the C++ which will create the LLVM IR found in source.s. I hope that helps. - Curtis On Jun 24, 2010, at 5:32 PM, Eli Friedman wrote: > 2010/6/24 Félix Cloutier <felixcca at yahoo.ca>: >> Hello everyone, >> >> I've been watching LLVM since about a year now, and I thought it was finally time I'd do something with it. So I've got my hands dirty with a cool project (who knows? maybe I'll end up releasing it), but since I'm fair...

Hello LLVMdev, I’m using LLVM to do static analysis exclusively (without any code generation). To implement this analysis, I’m using multiple address spaces to disambiguate the purpose of the pointed memory. Since address spaces never alias in my model, I set on to implement an alias analysis pass that would exactly provide this information, as I’m seeing a couple of otherwise dead store that

On Tue, Jul 6, 2010 at 9:08 AM, Greg Clayton <gclayton at apple.com> wrote: >> 2) Can I easily debug JIT'd code with LLDB? > > Are you running JIT'd code within another process that can be debugged (i.e. the simulation binary)? If so, you might want to have LLVM generate a full blown dylib, not just a JIT'd chunk of code and load the dylib using the standard shared

...virtual registers which i would like to update > if any virtual register does not exist since. You can check if any instructions are using it with MRI->reg_nodbg_empty(Reg). /jakob ------------------------------ Message: 22 Date: Tue, 22 Feb 2011 19:46:24 -0500 From: F?lix Cloutier <felixcca at yahoo.ca> Subject: Re: [LLVMdev] Can I use Clang to parse snippets of C++ code? To: Chris Lattner <clattner at apple.com> Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Message-ID: <5E4C34C9-B5D2-4F6C-819F-25E79E217479 at yahoo.ca> Content-Type: text/plain; charse...

> Instruction::insertBefore? Or if you prefer, you can mess with the > result of BasicBlock::getInstList() directly. There it is! I was looking for an equivalent to Instruction::insertBefore inside BasicBlock. (Something along the lines of BasicBlock::appendInstruction.) > You can cast your pointer to an integer, create an LLVM integer > constant, and create a constant cast from

Hey guys, Whys are there like 5 variants of CreateCall in IRBuilder<> with numbers appended to them? The only difference I can see is the number of arguments. Aren't C++ function overloads be suited for this? Félix

Hey guys, Is there a way to force the LLVM JIT compiler to omit the frame pointer in its generated i386/amd64 code? I've got a complex situation in which the stack can potentially be moved around so I'd prefer that the base pointer doesn't get pushed there. Félix

Hello guys, I have a project in mind that involves using the JIT for a few targets (x86 and x86_64 processors on Mac OS, Linux and Windows). However, there is an open bug that says LLVM generates incorrect code for Win64. Eli's last comment on the bug, however, says that it appears to be fixed. I don't have a Win64 box to test it. Can someone confirm that it now works (or still

Great! Are there other issues I should be aware of? Félix Le 2010-11-25 à 07:43:23, Anton Korobeynikov a écrit : > Hello Felix > >> I have a project in mind that involves using the JIT for a few targets (x86 >> and x86_64 processors on Mac OS, Linux and Windows). However, there is an >> open bug that says LLVM generates incorrect code for Win64. >> Eli's last