similar to: [LLVMdev] www.llvm.org seems to be down?

I've blown a couple of weekends trying to build under MinGW. I can build the llvm tools with only a couple of minor hassles, but can't seem to make any headway with the C Front End Most errors I run into involve not being able to find header files. The most frustrating part is that the error messages report that the file can't be found, and then proceed to give a path to where the

Is it safe to use the LLVM cfrontend 1.6 with LLVM 1.7 or the latest LLVM from CVS? I am running OS X 10.3.9, which I believe corresponds to Darwin kernel version 7.9.0. When I tried to use the 1.7 cfrontend, I could not get LLVM 1.7 or the LLVM from CVS to compile. However, when I used the 1.6 cfrontend (which is additionally labeled Darwin 7.9.0), I was able to get them to compile.

I am having some trouble getting llvm to build. I found some strange stuff going on in gcc/f/com.* In com.h I find ffeinfoKindType ffecom_gfrt_basictype ( ffecomGfrt ix); yet, in com.c I see ffeinfoBasicType ffecom_gfrt_basictype ( ffecomGfrt gfrt) I tried changing the line in com.h to ffeinfoBasicType ffecom_gfrt_basictype ( ffecomGfrt ix); and then doing make clean && make but I got a

Which version of gcc should be used to compile the cfrontend version 1.7? Thank you for your time, James Supancic -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060616/2b382d09/attachment.html>

I am trying to compile the cfrontend for gcc3, not gcc4. I did ./configure --prefix=/opt/llvmgcc --enable-languages=c,c++ After adding the --enable-languages flag I get "xgcc: installation problem, cannot exec `gccas': No such file or directory" It is true, I don't have gccas in my PATH, nor does the file gccas appear in my cfrontend directory. Is my configuration wrong, yet

On Fri, 16 Jun 2006, James Supancic wrote: > I am having some trouble getting llvm to build. > I found some strange stuff going on in gcc/f/com.* This sounds like you enabled the fortran frontend, which isn't supported. Please read the README.LLVM file in the root directory of the llvmgcc4 source distro. -Chris > In com.h I find > ffeinfoKindType ffecom_gfrt_basictype (

This is a forward of a question from the SourceForge LLVM forum. If anyone has experience with Cygwin and building the C front-end there, please reply and CC Alex. --- Post by Alex Vinokur below --- =============== Windows 2000 GNU gcc 3.3.3 (cygwin special) =============== ./configure ./make I have got compilation error ------------------------------- make[1]: Entering directory

Hi, When compiling the cfrontend for Linux/PPC architecture on a powermac G5, i got the following error : -------------------------------Compilation error listing if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi make GCC_FOR_TARGET="/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/xgcc -B/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/

On Sun, 05 Sep 2004 10:49:44 -0700 Reid Spencer <reid at x10sys.com> wrote: > Jeff, > > Actually, that was my fault. I forgot to remove the non-existent > directories from the configure.ac file. That's done and committed > now, so the advice is still the same: update configure script :) > > Reid. OK, no problems building. I got some minor issues with the simple

On May 4, 2004, at 10:36 PM, Chris Lattner wrote: > On Tue, 4 May 2004, Chris Lattner wrote: >> I suspect that a large reason that LLVM does worst than a native C >> compiler with the CBE+GCC is that LLVM generates very low-level C >> code, >> and I'm not convinced that GCC is doing a very good job (ie, without >> syntactic loops). > > Yup, this is

I just updated again (both llvm and llvm-gcc). The only thing that changed was: P test/Regression/CFrontend/2005-12-04-DeclarationLineNumbers.c The regression test below was done *with* your llvm-gcc changes to llvm- expand.c. I don't know what the failures are all about, but I will try it again. If its the same, I'll let you know. Reid. On Thu, 2006-04-13 at 16:20 -0500, Chris Lattner

The various intrinsic assert/crashes should all be fixed on mainline CVS (they are PR733, which I just fixed). The only ones that I'm wary of are: XPASS: /proj/llvm/build/../llvm/test/Regression/CFrontend/2004-02-20- StaticRedeclare.c.tr FAIL: /proj/llvm/build/../llvm/test/Regression/CFrontend/2005-12-04- DeclarationLineNumbers.c: In the former case, I would guess that the test isn't

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.

> Okay, I took a closer look at your output. > > I was correct in that gccas is attempting to assemble a native PPC > assembly language file. However, this appears to be happening because > the assembly file is generated by the GCC Makefiles for libgcc2 (in > llvm-gcc/gcc/config/rs6000/t-ppccomm, I think). > > The first thing I would try is Marco's suggestion: add

Cyrille Mescam wrote: > Hi, > > > When compiling the cfrontend for Linux/PPC architecture on a powermac > G5, i got > the following error : I hate to ask a silly question, but are you using "make bootstrap" to build the cfrontend? Your output looks like gccas is being given a native code assembly language file to parse, and I seem to recall that that happens if

LLVMers, On the way to resolving bug 122, I am committing my SymbolTable rewrite. If you are working on anything that uses the SymbolTable, I suggest you read the documentation in include/llvm/SymbolTable.h. The changes I've committed reduce the use of Type::TypeTy. This static member will go away in the future, so please do not propagate new code that uses it. There is no reason to use it

Hi, I was wondering whether anyone has attempted to port LLVM to windows running with a POSIX layer, such as cygwin? I recently tried to build and run llvm on cygwin, and I got the llvm tools working. There were a few problems in the configure script, namely the mmap test fails due to MAP_FIXED not working on windows (all other mmap() stuff works), which I simply commented out since its

Last night's nightly test has numerous new failures that can be attributed to the bug 122 changes. All these failures are related to the use of an outdated cfrontend build. The simple solution is to recompile the cfrontend. I ran into this also when I was testing the changes. The problem is that the bytecode read/written by the cfrontend is using an incompatible (partially between 1.2 and

Here's what's left on Linux (GCC 4.1.0), after all updates that went into the branch: Running /proj/llvm/build/../llvm/test/Regression/CFrontend/dg.exp ... FAIL: /proj/llvm/build/../llvm/test/Regression/CFrontend/2004-02-12- LargeAggregateCopy.c.tr: gccas: /proj/llvm/build/../llvm/lib/VMCore/Function.cpp:266: unsigned int llvm::Function::getIntrinsicID() const: Assertion `0 &&