similar to: [LLVMdev] new IA64 backend

Does anybody know if there is some tool to convert from WHIRL to LLVM? maybe some project under development? a similar project? Thanks > > --- Duraid Madina <duraid at octopus.com.au> wrote: > > Date: Fri, 18 Mar 2005 12:45:54 +0900 > > From: Duraid Madina <duraid at octopus.com.au> > > To: ahs3 at fc.hp.com, LLVM Developers Mailing List <llvmdev at

On Fri, 2005-03-18 at 05:04 +0900, Duraid Madina wrote: > I've just checked in an IA64 backend to LLVM! Woo hoo! And There Was Much Rejoicing in IA64 Land :-). -- Ciao, al ---------------------------------------------------------------------- Al Stone Alter Ego: Linux & Open Source Lab Debian Developer Hewlett-Packard

On Fri, 2005-03-18 at 05:04 +0900, Duraid Madina wrote: > Hi everyone, > > I've just checked in an IA64 backend to LLVM! Be warned, it's pretty > rough right now. Here are some of the known defects: > > - No varargs What are your issues here? Or are they simply at the "not implemented so I don't know" stage? Namely, I am working on some varargs

Andrew Lenharth wrote: > On Fri, 2005-03-18 at 05:04 +0900, Duraid Madina wrote: >> - No varargs > > What are your issues here? Or are they simply at the "not implemented > so I don't know" stage? The two bugs I mentioned (no varargs, no alloca) are pretty much two sides of the same coin: I'm ignoring the IA64 stack frame layout (for no good reason), so

> Itanium Everything checks out as expected. :) Duraid

Dear All, I've finished building binaries for the GCC frontends and am now testing the 1.5 release branch on i386/Linux, Sparc/Solaris, and PowerPC/MacOS X. I'm looking for volunteers to test LLVM 1.5 on platforms that we don't have in house. I'm specifically looking for people who can do: Itanium FreeBSD/i386 Windows (Cygwin, MingW, etc) I'm mainly interested in major

Oleg Smolsky wrote: > I've just tried building CVS/HEAD of llvm using gcc 4.0.0 that I have > installed to /opt/gcc ... then you should either add /opt/gcc/lib to /etc/ld.so.conf and rerun ldconfig, or add /opt/gcc/lib to your LD_LIBRARY_PATH . However, GCC 4.x definitely has issues building LLVM, at least on ia64. If you want to use LLVM in anger, I'd stick with 3.4 for now.

Hello Duraid, Duraid Madina wrote on Wednesday, 11 May 2005: >> I've just tried building CVS/HEAD of llvm using gcc 4.0.0 that I >> have installed to /opt/gcc > ... then you should either add /opt/gcc/lib to /etc/ld.so.conf and > rerun ldconfig, or add /opt/gcc/lib to your LD_LIBRARY_PATH . > However, GCC 4.x definitely has issues building LLVM, at least on > ia64. Oh,

Hi all, This is just to announce that I have a FreeBSD x86 machine running the test suite more or less continuously: http://kinoko.c.u-tokyo.ac.jp/~builddonkey/ Of note is that it now runs Dejagnu tests. (Thanks, tonic+co!) I'm also tracking CVS breakage (internally, for now). At some later point, I'll make available more real-time information on "is CVS alive and if not,

On Fri, 18 Mar 2005, Duraid Madina wrote: >>> - No instruction scheduling/bundling of any sort >> >> So this one needs to be coordinated. Next week, I might see about >> adding MachineInstruction support to the SelectionDAG so you can load up >> a DAG post-ISel and then spit it back out scheduled. > > That would be much appreciated, particularly if it

On Wed, Jun 01, 2005 at 10:50:35AM -0400, Bill Wendling wrote: > It didn't look like there was a cftonend binary for the IA-64 > platform. Are we supposed to use the x86 binaries instead? The answer to that is that we don't have IA-64 in-house, so we don't provide an IA-64 C/C++ front-end, but if someone were to contribute it to us, we would gratefully host it. Note that if you

Hi Misha, On 6/1/05, Misha Brukman <brukman at uiuc.edu> wrote: > On Wed, Jun 01, 2005 at 10:33:39AM -0400, Bill Wendling wrote: > > What's the plan for support on Linux 64-bit machines? Is that actively > > being worked on right now or is there a roadmap for doing this? > > Do you mean compiling on 64-bit Linux or generating code for 64-bits? > I meant

So, I'm trying to build everything from source for the Debian package for LLVM, including the C/C++ front end. I'm running this build on LLVM 1.4 source (the released tarball), using Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64 box, dual CPU). Before I get _too_ deep into it, I thought I would ask if the following compilation failure on the CFE looks the least bit familiar

Hi, For the PyPy project ( http://codespeak.net/pypy ) I am working on the x64-64 support. I would like to use llc -march=ia64 to generate the assembly but that is not supported at the moment. As a workaround I let llc generate C code that gets compiled, but this unfortunately is not a good way to show the power of llvm. A understood this ia64 support will be worked on soon. First week of july

Hi there, The IA64 architecture, which had its 'official' name changed to the "Itanium Processor Architecture", *is* supported by llc. I am pretty sure you are talking about the x86-64 architecture, which has also had its share of unfortunate name changes and is also known as "AMD64", "EM64T" and all sorts of things in between. x86-64 is *not* currently

On Wed, 2005-06-01 at 10:04 -0500, Misha Brukman wrote: > On Wed, Jun 01, 2005 at 10:50:35AM -0400, Bill Wendling wrote: > > It didn't look like there was a cftonend binary for the IA-64 > > platform. Are we supposed to use the x86 binaries instead? > > The answer to that is that we don't have IA-64 in-house, so we don't > provide an IA-64 C/C++ front-end, but

You are right, the machine I am on is a AMD Opteron. I could probably generate working code for x86, but I am testing the implications of using 64 bits integers. The four weeks is not really important, it's just that it would be nice to have really fast code to showcase. Something related to this: to test the effect of 64 bits integers I replace all reference of int by long in my .ll file.

yes, so this happens on anything that uses a struct for va_list (like alpha). I am currently working on fixing this. if you look at the last patch to the alpha portion of llvm-gcc, you can see a quick hack to work around that (aka, get it to compile), but the resultant compiler will have issues with varargs. Alternately, build ia-32 binaries on x86_64, llvm-gcc is happy with the the abi there.

Hi, everybody: I am a beginner with LLVM, in fact today was the first day that I use it. I have several questions about LLVM: Can I use LLVM to compile several files (bytecode), scripts (char*) and link them with external libraries generating *only* one executable (all in memory)? Can I invoke externals functions from a guest (LLVM generated) code which exist in the host code (the code that

On Thu, 10 Mar 2005, Andrew Lenharth wrote: > yes, so this happens on anything that uses a struct for va_list (like > alpha). I am currently working on fixing this. if you look at the last > patch to the alpha portion of llvm-gcc, you can see a quick hack to work > around that (aka, get it to compile), but the resultant compiler will > have issues with varargs. While Andrew is