similar to: [LLVMdev] Compile llvm-gcc fortran backend using mingw

And how about this one for handling the C specific invoke_impl_ptr_type? Index: gcc-4.2.llvm/gcc/c-common.h =================================================================== --- gcc-4.2.llvm.orig/gcc/c-common.h 2008-07-30 21:01:49.000000000 +0200 +++ gcc-4.2.llvm/gcc/c-common.h 2008-07-30 21:01:56.000000000 +0200 @@ -1164,7 +1164,6 @@ extern struct block_sema_info *cur_block; extern tree

Hi Pavel, > BTW, it is little bit strange that llvm-gcc doesn't support CMake building system. > LLVM does and it is extremely convenient.... llvm-gcc is dead, deprecated in favour of clang and dragonegg. It won't be part of the upcoming 3.0 release. This is why no-one is interested in working on it. Ciao, Duncan.

Thank you for quick reply. I see, llvm-gcc is frozen.... Is there Fortran front-end for LLVM then? On Mon, Oct 17, 2011 at 5:09 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Pavel, > > > BTW, it is little bit strange that llvm-gcc doesn't support CMake > building system. > > LLVM does and it is extremely convenient.... > > llvm-gcc is dead, deprecated

> > .... but some Pure users and many of my students do. Pure relies on > LLVM-capable compilers for its C/C++/Fortran > inlining capabilities, so being able to just point Windows users to a > binary llvm-gcc package to make that work is very convenient. Nice to be called "Pure" :-) especially with capital letter. MinGW binaries for llvm-gcc don't have Fortran

On Jul 30, 2008, at 11:39 AM, Duncan Sands wrote: > On Wednesday 30 July 2008 18:13:27 Duncan Sands wrote: >> On x86-64 linux, in stage 2, I get: >> >> c++ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict- >> prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno- >> variadic-macros -Wno-overlength-strings -Wold-style-definition - >>

Hi Albert, > On 10/17/2011 10:09 AM, Duncan Sands wrote: >> llvm-gcc is dead, deprecated in favour of clang and dragonegg. It won't be part >> of the upcoming 3.0 release. This is why no-one is interested in working on it. > > The tentative release notes still say otherwise: "LLVM 3.0 will be the > last release of llvm-gcc."

On 10/17/2011 02:00 PM, Duncan Sands wrote: > this was a result of someone replacing 2.9 with 3.0 everywhere in that doc. > If you check the 2.9 release notes you will see that this was announced in > 2.9 release. Ah, I should have thought of that. :) > The 3.0 version does not require a patched gcc-4.5. It also works with > gcc-4.6. It does have its rough spots, but they were

PS: A more convincing (IMO) argument against dragonegg is that it doesn't work on windows. That's because the gcc plugin architecture doesn't work on windows. Takumi has been thinking about this and has been enable to get dragonegg to work on windows anyway using some clever tricks.

Hi Pavel, > Is there Fortran front-end for LLVM then? yes, dragonegg: http://dragonegg.llvm.org The development version (i.e. the upcoming 3.0 release) works better than llvm-gcc ever did. Ciao, Duncan.

On 10/17/2011 10:09 AM, Duncan Sands wrote: > llvm-gcc is dead, deprecated in favour of clang and dragonegg. It won't be part > of the upcoming 3.0 release. This is why no-one is interested in working on it. The tentative release notes still say otherwise: "LLVM 3.0 will be the last release of llvm-gcc." (http://llvm.org/docs/ReleaseNotes.html) I understand that llvm-gcc

Hi Duncan, On 10/17/2011 04:44 PM, Duncan Sands wrote: > PS: A more convincing (IMO) argument against dragonegg is that it doesn't > work on windows. That's because the gcc plugin architecture doesn't work > on windows. Takumi has been thinking about this and has been enable to > get dragonegg to work on windows anyway using some clever tricks. Interesting, thanks for

2011/10/18 Albert Graef <Dr.Graef at t-online.de>: > On 10/17/2011 04:44 PM, Duncan Sands wrote: >> PS: A more convincing (IMO) argument against dragonegg is that it doesn't >> work on windows.  That's because the gcc plugin architecture doesn't work >> on windows.  Takumi has been thinking about this and has been enable to >> get dragonegg to work on

Hi, Currently we are running CentOS 4.x on a 2-way Opteron machine. This machine, through a SCSI host adapter (Adaptec), is connected to a 2TB storage unit (an external RAID-5 disk array) Until our recent unintentional power trip, everything was fine and smooth. We have been experiencing complication accessing the storage ( it could be either intermittent filesystem error, partition could not be

I'm trying to cross-compile LLVM with build=, host=target=. I'm using the following packages from Debian lenny: mingw32 4.2.1.dfsg-1 mingw32-binutils 2.18.50-20080109-1 mingw32-runtime 3.13-1 The first problem I hit was when I configured with CC, CXX, AR and RANLIB set to mingw cross-tools, but forgot to specify NM as well. This resulted in a load of warnings that scrolled off the

Hi! ---- Did anyone thought about shipping QEMu as part of Solaris Nevada (via SFWNV) yet ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;)

This is from work that Manman did. I thought she'd fixed this particular issue though. Can you file a bug with a test case please? On Nov 5, 2013 10:10 AM, "lipengcheng" <pli at cs.rochester.edu> wrote: > Hello LLVM, > > I encountered the following bugs when I compiled my program in debug > version. > Could someone help me with that ? Really appreciate that.

Albert Graef <Dr.Graef at t-online.de> writes: > On 06/21/2012 04:22 PM, Óscar Fuentes wrote: >> About the "many features" that cmake lacks, can you provide a list, >> please? > > Generally it works fairly well, but here are some differences to the > autoconf-based build I noticed: > > - No 'make uninstall'. That is a real deal breaker if you

Hi R-users, I am trying to divide a vector (say X) into equal frequency bins. If one uses the hist() function, then a histogram is plotted, but with bins of equal widths, and not with bins having the same number of data points. I have then tried the histogram() function as follows: histogram(X, nint=10, breaks=NULL, equal.widths=F) This works as I want. However, I can't extract which

Hi, What version of clang are you using? I think r174785 is the fix. Manman On Tue, Nov 5, 2013 at 11:04 AM, lipengcheng <pli at cs.rochester.edu> wrote: > What do you mean by test case please ? Using the following commands to > compile mcf program > can reproduce such issue all the time. > > Probably it is my version's problem. Because I checked out 3.3version from

Hello LLVM, I encountered the following bugs when I compiled my program in debug version. Could someone help me with that ? Really appreciate that. Thanks, Take the mcf program in SPEC2K6 as example. The compiling options are : clang -O0 -c -emit-llvm -o obj/mcf.o -g -DSPEC_CPU mcf.c llvm-link -o mcf.bc obj/mcf.o opt -o mcf.opt.bc mcf.bc -O2 llc -O0 -relocation-model=static -o mcf.s