similar to: [LLVMdev] gcc, conceptgcc, and llvm-gcc

Hi Xiaolong, > My previous work was done mainly in the front-end of conceptgcc, > whereas recently I am doing some code analysis in the middle-end of > llvm. I am considering to port my previous work to llvm. > > So, I am very concerned with the difference between gcc and llvm-gcc, > and of course the difference between gcc and conceptgcc. I have no > idea of the former

I am trying to build llvm-gcc-4.2 but cannot figure out how to get past the problem described below. Any help will be much appreciated. Regards Roger gnatbind -C -I- -I. -Iada -I../../llvm-gcc-4.2/gcc/ada -o ada/b_gnat1.c -n ada/gnat1drv.ali error: "s-imenne.adb" must be compiled error: ("/opt/gnat-gpl-2009/lib/gcc/i386-apple-darwin10.2.0/4.3.4/adalib/s-imenne.ali" is obsolete

Hi Roger, > I am trying to build llvm-gcc-4.2 but cannot figure out how to get past the problem described below. you need to build with GNAT GPL 2007 or earlier, as described here: http://llvm.org/docs/GCCFEBuildInstrs.html This is because llvm-gcc-4.2 is based on gcc-4.2, and you have the same problem with gcc-4.2. I don't know if anyone ever built an Ada-enabled llvm-gcc on MacOS

Hi all, Considering the limit time I have for an implementation, I better ask for your inputs on a few questions. Any answer is to be much appreciated. First, how does LLVM handle the "new statement" of C++? Could any one give me any hint? Second, what properties does the callgraph generated by LLVM has? One property I am interesting in is whether the callgraph is a safe

The current dragonegg trunk svn used under FSF gcc 4.5.2 with llvm 2.9 is able to bootstrap FSF gcc 4.5.2 itself on x86_64-apple-darwin10... Using built-in specs. COLLECT_GCC=gcc-mp-4.5 COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin10/4.5.2/lto-wrapper Target: x86_64-apple-darwin10 Configured with: ../gcc-4.5.2/configure --prefix=/opt/local --build=x86_64-apple-darwin10

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

Duncan, Here are the complete benchmarks rerun against gcc 4.5.4 built with... Using built-in specs. COLLECT_GCC=gfortran-fsf-4.5 COLLECT_LTO_WRAPPER=/sw/lib/gcc4.5/libexec/gcc/x86_64-apple-darwin11.0.0/4.5.4/lto-wrapper Target: x86_64-apple-darwin11.0.0 Configured with: ../gcc-4.5.4/configure --prefix=/sw --prefix=/sw/lib/gcc4.5 --mandir=/sw/share/man --infodir=/sw/lib/gcc4.5/info

On Thu, Jun 09, 2011 at 03:44:40PM +0200, Duncan Sands wrote: > Hi Jack, thanks for doing this. > >> Below are the tabulated compile times and executable sizes. >> >> A) gcc 4.5.4svn using -msse3 -ffast-math -O3 -fno-tree-vectorize >> B) gcc 4.5.4svn/dragonegg using -msse3 -ffast-math -O3 -fno-tree-vectorize -fplugin-arg-dragonegg-enable-gcc-optzns >> C)

Hi everyone, I'm very new to the world of compilation and I've got to spend some time time on LLVM. As I have to produce a cross compiler for a completely new target and I don't want to cross-build the binutils, I choose Clang as a replacement frontend for llvm instead of llvm-gcc. But first, I just would like to compile something on my Linux platform in order to test the software,

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.

Hello, how would I go porting llvm-gcc-4.2 to an “unknown” platform, i.e. MirBSD? For regular gcc, I’d have to add stuff to gcc/gcc/config/ and patch quite some configure scripts, but seeing that llvm-gcc uses LLVM for target specific stuff, how much of this still applies? cpp defines and startup files at the least, probably, for the com- piler driver… Which dependencies does llvm-gcc-4.2 have,

Hello Reid, Thanks. > Yes, it's an integral part of the Instruction. You can change it by > providing a name when you create the instruction. Following your hint, can I understand in this following way? The name (denoted by "<result>") is actually a referrer to the instruction . Consider this instruction: %this_addr = alloca %struct.String* ;

Dear all, I'm trying to use LLVM 2.7 (running on a x86-32 platform) as cross compiler to build ADA programs that will run on a different target platform (PowerPc). The LLVM documentation states that: "The only platform for which the Ada front-end is known to build is 32 bit intel x86 running linux. It is unlikely to build for other systems without some work." and also: "The

Yes, it's an integral part of the Instruction. You can change it by providing a name when you create the instruction. Reid On Thu, Jun 10, 2010 at 8:34 AM, Xiaolong Tang <xiaolong.snake at gmail.com> wrote: > Hi all, > > In the language specifications, many instructions have this form: > >  <result> = ... > > So, where is "<result>" defined?

Good evening, Tang. > What is the type of the first operand of the instruction (i.e., > getOperand(0))? It might be ConstantExpr. You may use dyn_cast<GEPOperator>(getPointerOperand()). Also GetElementPtrInst* can be casted to GEPOperator. ...Takumi 2010/6/18 Xiaolong Tang <xiaolong.snake at gmail.com>: > > Hey, > > Considering the following instruction: >

Hello everyone! I got following error while trying to compile llvm-gcc-4.2 using mingw: ..\llvm-gcc-4.2\obj\libcpp/../../libcpp/macro.c:1165: undefined reference to `flag_iasm_blocks' stub-c.o:stub-c.c:(.debug_info+0x81a0): undefined reference to `flag_iasm_blocks' stub-c.o:stub-c.c:(.debug_info+0x81b9): undefined reference to `iasm_state' stub-c.o:stub-c.c:(.debug_info+0x81d8):

On Fri, Jun 15, 2012 at 09:06:03AM +0200, Duncan Sands wrote: > Hi Dima, > > > FWIW, attached presentation provides a simple jump-start tutorial for newbies to > > start doing something useful with LLVM, DragonEgg, NVPTX backend and some custom > > high-level language. Along with short software overview from the user > > perspective it contains instructions on

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 -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -o f951 \ fortran/arith.o fortran/array.o fortran/bbt.o fortran/check.o fortran/data.o fortran/decl.o

> > 4. Running Fortran, Ada, C/C++/ObjC tests as well with test results emailed > > to the llvm-testresults. > > Are these different or new tests? Why wouldn't they just be a part of the > llvm-test module? Then you don't have to do any modifications to the > scripts. Probably means the gcc testsuite. Ciao, Duncan.

llvm (and clang) do not include binutils. You're seeing clang invoking the gcc shell to assemble the .s file that clang generated, then again to link the object file into an executable. On Apr 27, 2010, at 8:31 AM, Swiss Guy wrote: > > Hi everyone, > > I'm very new to the world of compilation and I've got to spend some time > time on LLVM. > As I have to produce