similar to: [LLVMdev] enabling Debian x86_64 for llvm 1.7

I'm getting the error below on Ubuntu Hardy on ia32 on r55688. John make[3]: Entering directory `/home/regehr/llvm-gcc/build/gcc' gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I../../gcc

Hi > Right it does. However, does something *else* require MParSchedule? If > so, what? Ok, i am writing on a different backend based on the cbackend. The test usage of this pass looks like this: void getAnalysisUsage(AnalysisUsage &AU) const { AU.addRequired<LoopInfo>(); AU.addRequired<MParSchedule>(); AU.setPreservesAll(); } and then in the

The saga continues. I've been tracking the interface changes and merging them with the refactoring work I'm doing. I got as far as building stage3 of llvm-gcc but the object files from stage2 and stage3 differ: warning: ./cc1-checksum.o differs warning: ./cc1plus-checksum.o differs (Are the above two ok?) The list below is clearly bad. I think it's every object file in the

Dear Nico, I believe you need to add LLVMipa to the list of libraries to link into your tool. FindUsedTypes::ID is defined in lib/Analysis/IPA. I think it would be LLVMipa.a if you added it to LLVMLIBS and ipa if you added it to LINK_COMPONENTS. -- John T. Nico wrote: > Hi, > > I tried to implement an 'llc'-like tool in my project to manage > different passes and a

Hi, Looking into LLVM for a database query engine project... After downloading the latest source from CVS, it's my first time trying to build LLVM. Following the "Getting Started" instructions, all went well until gmake reported this error while trying to link llc: In function `(anonymous namespace)::BreakCriticalEdges::getAnalysisUsage(llvm::AnalysisUsage&) const':

Dear John, thanks! I was irritated by the path of the header file/declaration. It is not like the definition in a subdirectory. Sorry my fault. Is there an overview where classes and link options are mapped to each other? Kind regards, Nico On Jan 4, 2009, at 4:07 PM, John Criswell wrote: > Dear Nico, > > I believe you need to add LLVMipa to the list of libraries to link >

On Tue, 25 Oct 2005, Kurt Harriman wrote: > Looking into LLVM for a database query engine project... > > After downloading the latest source from CVS, it's my first time trying > to build LLVM. Following the "Getting Started" instructions, all went well > until gmake reported this error while trying to link llc: > AFAICT, 'LoopSimplifyID' does in fact

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

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.

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

Hi, I tried to implement an 'llc'-like tool in my project to manage different passes and a target machine. I use given llvm project structure to avoid problems but I have a link problem and don't know how to solve it: The target machine uses 'FindUsedTypes' pass and when I try to use my target machine in the tool I got "Undefined symbols:

Anyone willing to do some testing? I've finally gotten LLVM 1.4 to build Debian packages from source (it weren't pretty), at least for i386. To get the debs, add the following to your sources.list: deb http://toolchain.org/~ahs3 / deb-src http://toolchain.org/~ahs3 / then 'apt-get update' as usual. To install the packages: apt-get install llvm llvm-doc This will

On Fri, 11 Mar 2005, Markus F.X.J. Oberhumer wrote: > Chris Lattner wrote: >> 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

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

On Apr 27, 2007, at 3:50 PM, David Greene wrote: > The saga continues. > > I've been tracking the interface changes and merging them with > the refactoring work I'm doing. I got as far as building stage3 > of llvm-gcc but the object files from stage2 and stage3 differ: > > > warning: ./cc1-checksum.o differs > warning: ./cc1plus-checksum.o differs > >

So. I _finally_ got the building and packaging of LLVM and the GCC FE into a state I'm more or less happy with. As a result, I uploaded x86 packages into the NEW queue just a little while ago. Whew. What this means is that in a few weeks (hard to say how long, really) the package will be reviewed by the Debian FTP masters. If they like/approve of what they see, they'll let the package

On Sun, 2006-10-29 at 19:39 -0500, Adam Goode wrote: > Hi, > > I'm still working on the Fedora Extras package for LLVM. > > Because of the Fedora requirement that all packages in Extras be built > from source, I must build the dreaded C Front End. :) > > I think I've mostly got things set up correctly, but I've found what I > suspect is a tricky problem:

On 2008-09-29 07:46, Keun Soo Yim wrote: > Does anyone succeed at compiling Linux kernel for Sparc v8 architecture? > I am currently trying to expand the regime of LLVM to Sparc kernel codes. > The following is the initial error messages. Any comment is welcomed. > > #1. Inline Assembly > > > > Code: > > register struct thread_info

On Fri, 11 Mar 2005, Al Stone wrote: > So. I _finally_ got the building and packaging of LLVM and the > GCC FE into a state I'm more or less happy with. As a result, I > uploaded x86 packages into the NEW queue just a little while ago. > Whew. Nice! Thanks a lot Al! -Chris > What this means is that in a few weeks (hard to say how long, > really) the package will be

So the fundamental problem I'm trying to solve is how get my cfrontend build configured properly. The usual symptom of an incorrect configuration is the inability to find various header files. Here's some example spew: $ /home/llvm_home/llvm-gcc-build/gcc/xgcc -v -B/home/llvm_home/llvm-gcc-build/gcc/ -Bc:/msys/1.0/mingw32/bin/ -Bc:/msys/1.0/mingw32/lib/ -isystem