search for: alvarocastro

...first version was working perfectly. > > > I would really appreciate if someone could give me a clue of what I'm > > doing wrong... > > > Thank you, > > > Bests, > > -- > |||||||||||||||||||||||||||||||||||||||||||||||||||||||| > > >http://www.alvarocastro.es > > _______________________________________________ > LLVM Developers mailing list > LLVM... at cs.uiuc.edu        http://llvm.cs.uiuc.eduhttp://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

...;t track it with gdb. The first version was working perfectly. > > > I would really appreciate if someone could give me a clue of what I'm > doing wrong... > > Thank you, > > > Bests, > -- |||||||||||||||||||||||||||||||||||||||||||||||||||||||| > http://www.alvarocastro.es

Hi, Long time ago (llvm-svn june 2008) I asked here about a way to output the assembly code of my JIT generated code to a string, so I could use it to read it on the screen. I came up with this solution: std::string Err; const llvm::TargetMachineRegistry::entry* _arch = llvm::TargetMachineRegistry::getClosestTargetForJIT(Err); std::string FeaturesStr; llvm::TargetMachine*

Dear Maxime, Nyx wrote: > Hello, > > I would like to know how to go about printing the x86 assembly output for a > compiled function (I'm using the JIT). I saw there is a X86IntelAsmPrinter > on doxygen. However, it takes several arguments I don't know how to fill in. > Is there a helper function to create such a pass? Once I have the pass > created, do I just add it

Hello, How would you implement an Erlang feature such as the ultra-light processes? Is llvm prepared for similar situations? I would appreciate some insight on this. Thank you very much, .alvaro.castro.castilla.

Hi Álvaro, Your question is too vague to answer with any accuracy. Could you be more specific? -bw On Jul 24, 2008, at 1:08 PM, "Álvaro Castro Castilla" <alvaro.castro.castilla at gmail.co m> wrote: > Hello, > > > How would you implement an Erlang feature such as the ultra-light > processes? > Is llvm prepared for similar situations? > > I would

...> - Simon > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > -- |||||||||||||||||||||||||||||||||||||||||||||||||||||||| > http://www.alvarocastro.es

Hello, I would like to know how to go about printing the x86 assembly output for a compiled function (I'm using the JIT). I saw there is a X86IntelAsmPrinter on doxygen. However, it takes several arguments I don't know how to fill in. Is there a helper function to create such a pass? Once I have the pass created, do I just add it to a FunctionPassManager? Thank you for your time, -

...llvmdev > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > -- |||||||||||||||||||||||||||||||||||||||||||||||||||||||| > http://www.alvarocastro.es

2008/7/24 Owen Anderson <resistor at mac.com>: >> * They are isolated and the only way to exchange information is >> message passing >> > This one is hard to guarantee in a compiled context, unless you > implement a lot of stuff to track pointer values. Remember, all of > these threads will be sharing an address space. If you want true > protection, you'll

Hi Kenneth, If the LLVM project is switching to CMake, then CTest might be the framework of choice to use rather than scripting up something in Bash. --Sam --- On Wed, 7/30/08, Kenneth Boyd <zaimoni at zaimoni.com> wrote: > From: Kenneth Boyd <zaimoni at zaimoni.com> > Subject: Re: [LLVMdev] Is there room for another build system? > To: "LLVM Developers Mailing