similar to: [LLVMdev] Could LLVM help me?

> You are the only one who response my problem. The others maybe don't > understand my questions....:( I'm also replying to the list. People are very nice and helpful! Plus, I am on vacation! :) > well....my questions are following. > 1. I wrote a very simple backend, but I dont know how to tell the llvm > compiler to use it. > I found something in "llc

Paolo Invernizzi wrote: > There was a similar problem some time ago, and was resolved with alloca. > I think it's a better solution to use the stack instead of the heap... I tend to agree, but the constructors won't get called if it's an object array -- anyway, this particular case there was no objects, just pointers and bools so alloca should be fine. I'll leave it to

Chris Lattner wrote: > Can you explain what goes wrong without the stub? It's the only part that > I didn't apply. The X86 backend doesn't get registered since there are no references to symbols in X86TargetMachine the object file is never pulled in from the library I create, and thus the static intializer for the RegisterTarget is never called...

Hi, I'm developing a very basic new LLVM backend for a RISC machine (named Risco), based on the existing Sparc and Mips backends and the main tutorial [1]. I'm having trouble registering the backend so the main tools can see it. My project code is outside the source tree, and I've altered the Makefile to generate a shared library for the backend (libLLVMRiscoCodeGen.so). I've

On Mon, 18 Oct 2004, Morten Ofstad wrote: > To reduce the number of mails, I also include my next patch -- X86 > specific code and inline assembly for Visual C, unfortunately I had to > use the nasty IncludeFile trick again to get the linker to work.. I applied most of this here: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041018/019493.html Can you explain what goes

On Mon, 18 Oct 2004, Morten Ofstad wrote: > Chris Lattner wrote: > > Can you explain what goes wrong without the stub? It's the only part that > > I didn't apply. > > The X86 backend doesn't get registered since there are no references to > symbols in X86TargetMachine the object file is never pulled in from the > library I create, and thus the static

I'm having a go at writing an LLVM backend for the WDC 65816. The documentation page on writing an LLVM backend<http://llvm.org/docs/WritingAnLLVMBackend.html>gives this example of target registration: extern "C" void LLVMInitializeSparcTargetInfo() { RegisterTarget<Triple::sparc, /*HasJIT=*/false> X(TheSparcTarget, "sparc",

Dear John, Thank you so much for your help. I looked at those documents. Could you kindly answer the following questions: Does it mean that I have to make my own backend target in order to write a machine pass even if I want to run a simple machinefunction pass? for example,if I want my pass to get MIPS instructions as an input, I have to copy all the files from mips target and add a file to it

Yes, I have done exactly the same. The wawanalyzer is the same. I changed ARM.h and ARMTargetMachine.cpp in the tager/arm folder. then I make tool/llc and lib folder. On Tue, Nov 17, 2015 at 10:55 AM, John Criswell <jtcriswel at gmail.com> wrote: > On 11/17/15 12:16 AM, fateme Hoseini via llvm-dev wrote: > > Hi, > So, I run my pass in X86 target with llc command and it printed

Hi, So, I run my pass in X86 target with llc command and it printed out "hello****". Now I am trying to do the same pass for ARM target. So I did exactly what I did for X86 as mentioned in my previous posts. When I run the following command: llc -march=arm test.ll -o test nothing prints out. I did the same for MIPS target too and I got no result. Can anyone tell me what I'm doing

On May 19, 2008, at 9:13 PM, Razvan Aciu wrote: > I tested this pre-release on MSVC and I noted that none of the > submitted > patches (mine or others) were applied. > So the llvm 2.3 will not compile out of the box in MSVC? > Please provide me with a link to the patch(s) that need to be applied (llvm-commits archive email). I only apply patches that have been sent to me and

Yes, I am working on it. The sub-projects are still having issues but the other documentation has been fixed. -Tanya > On Feb 14, 2019, at 3:53 AM, Alexander Kornienko <alexfh at google.com> wrote: > > Tanya, friendly ping. > > On Mon, Feb 11, 2019 at 3:21 PM Alexander Kornienko <alexfh at google.com <mailto:alexfh at google.com>> wrote: > Hi Tanya, >

Thank you so much. That helped alot. Fami On Wed, Nov 4, 2015 at 9:40 AM, John Criswell <jtcriswel at gmail.com> wrote: > On 11/3/15 7:54 PM, fateme Hoseini wrote: > > Dear John, > Thank you so much for your help. I looked at those documents. Could you > kindly answer the following questions: > > Does it mean that I have to make my own backend target in order to write

Just a reminder, please complete your testing by May 21st! Thanks, Tanya ---------- Forwarded message ---------- Date: Tue, 13 May 2008 00:25:41 -0700 From: Tanya Lattner <tonic at nondot.org> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: 2.3 Pre-release available for testing LLVMers, The 2.3 pre-release is available for testing:

Thank you! It seems like new changes in .rst files are picked up quickly now. -- Alex On Thu, Feb 14, 2019 at 7:33 PM Tanya Lattner <tonic at nondot.org> wrote: > This should all be fixed now. > > Thanks, > Tanya > > > On Feb 14, 2019, at 9:50 AM, Tanya Lattner <tonic at nondot.org> wrote: > > Yes, I am working on it. The sub-projects are still having

On Jan 26, 2013, at 3:20 PM, Tanya Lattner <tonic at nondot.org> wrote: >>> >>>> I agree that the list name is redundant and should be dropped, but >>>> the revision number is compact and very useful... >>>> >>>> -Chris >>> >>> If we agreed to perform this change and we found the person who can change >>>

This is my patch for MSVC 2008 and it was applied by Chris: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080512/062390.html I tested it and it is ok for the 2.3 release. Razvan ----- Original Message ----- From: "Tanya Lattner" <tonic at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, May 20, 2008 7:40 AM

LLVMers, The 2.5 pre-release2 is finally available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run

Thanks for testing the release. Overall the test results look decent with a couple exceptions. You also have a few CBE failures that I am not seeing. What version of xcode do you have installed? Can you send me the following files? SingleSource/Regression/C/Output/2008-01-07-LongDouble.* SingleSource/Regression/C/Output/PR1386.* Thanks, Tanya On Jan 26, 2008, at 6:43 AM, Takanori Ishikawa