similar to: [LLVMdev] Hello World crashes!

Hi, Sorry for the newbie question. I downloaded llvm and tried out the simple "Hello, World" program but got the following error. What am I missing? I am running RHAS 3 Update 4 with GCC 3.2.3. Thanks, Bharadwaj $ ./hello lli: /home/proj/skokomish/syadaval/ia32/Sandbox/llvm/lib/Target/X86/X86CodeEmitter.cpp:208: unsigned char ModRMByte(unsigned int, unsigned int, unsigned int):

This attempts to address http://llvm.org/bugs/show_bug.cgi?id=18220 It also fixes a test which was requiring the *wrong* output. I'm relatively happy with this part, and it even solves most of the hard part of feature request for .code16 in bug 8684 — which was actually why I started prodding at this. But I could do with some help with the 16-bit signed relocation handling, which I've

Hi David, I'm catching up on email at the moment so I don't know if you've done this, but patches should go to llvm-commits for review if you wouldn't mind. Thanks! -eric On Thu Dec 12 2013 at 8:39:19 AM, David Woodhouse <dwmw2 at infradead.org> wrote: > This attempts to address http://llvm.org/bugs/show_bug.cgi?id=18220 > It also fixes a test which was requiring

Hi there, Is it possible to use GCC 3.4 with LLVM 2.0? I tried to compile GCC 3.4 with LLVM 2.0 and get following error message: /scratch/spa_llvm-2.0/llvm-gcc3.4-1.9.source/build/gcc/xgcc -B/ scratch/spa_llvm-2.0/llvm-gcc3.4-1.9.source/build/gcc/ -B/scratch/ spa_llvm-2.0/llvm-gcc3.4-1.9.source/install/i386-pc-solaris2.11/bin/ - B/scratch/spa_llvm-2.0/llvm-gcc3.4-1.9.source/install/i386-pc-

Chris Lattner wrote: > Patches welcome. Please send a patch, or even just some suggested > text, and we'll be happy to include it. Remember that the people who > usually end up writing the FAQ's already know all the answers, so it's > hard for us to see things from fresh perspectives sometimes :) > > -Chris > Actually, my request for more info in the

Hi, all, Samba version 3.2.1 tar ball is downloaded. Next, I'm facing how to configure it for ARM Linux, but it's not so smooth for me. : ( The following is my environment information: 1. Development environment : Linux PC 2. Cross compiler : scratchbox/compilers/arm-gcc3.4-uclibc0.9.28 3. Configure options : (almost of them are googled) $ ./configure --without-krb5

Hi, Sorry for the newbie question. I downloaded llvm 1.8a and llvm-gcc3.4-binary, tried out the simple cpp program like this: #include <iostream> using std::cout; using std::endl; int main() { cout << "Hello World" << endl; return 0; } but got the following error: lli((anonymous namespace)::PrintStackTrace()+0x15)[0x85c4d85]

Erick Tryzelaar wrote: > Actually, my request for more info in the "Getting Started" had some > hidden questions, as I don't know the answer to them :) So to be a > little more clear, here are the two I had: > > Does the gcc4 no longer need the "fixheaders" script that the gcc3.4 > frontends uses? > > Is it possible to install both the gcc4 and

Hello, It looks like the "Getting Started" is missing some info about the gcc 4.0 frontend. Since it doesn't follow the setup of the cfrontend/gcc3.4 package, a couple sections describing the front end don't cover the gcc4 package. Here are the couple things I'd wish could be fleshed out a bit more: Under "Getting Started Quickly (A Summary)", it'd be nice

I'm really sorry for the wide e-mail, but I've exhausted the normal channels. I get: llvm[2]: Linking Release executable tblgen (without symbols) llvm[2]: ======= Finished Linking Release Executable tblgen (without symbols) llvm[2]: Compiling fpcmp.cpp for Release build llvm[2]: Linking Release executable fpcmp (without symbols) llvm[2]: ======= Finished Linking Release Executable

Hi, The attached small path fixes X86InstrInfo::getMemModRMByteSize to be consistent with the emit code in X86CodeEmitter::emitMemModRMByte on amd64. Zoltan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090408/ad831982/attachment.html> -------------- next part -------------- A non-text

Hi all, at my paid job I am pushing the Clang/LLVM combo into evaluation (we currently use a gcc3.4 generation toolchain). Since we produce for the embedded domain we need a reliable host (i.e. simulation i686) / target (PPC) dual setup. To this end I almost succeeded grinding through our large(ish) codebase but found some PPC snags. I filed these bugs, complete with repro IR code:

I am interested in analyzing the bytecode code produced for C files. By default, inlining of user and library functions (libc) is done. If I turn off inlining (-disable-inlining in gccas and gccld) then no inlining is done. I want to be able to inline user code but disallow library code to be inlined. In trying to understand the InlineSimple.cpp code, I see that library functions are

On Thu, 21 Feb 2008, Dale Johannesen wrote: > The defined gcc interface for this is -fno-builtin. It seems not be > to be working in llvm-gcc, however. Please file a reduced testcase in bugzilla, -Chris > >> I am interested in analyzing the bytecode code produced for C files. >> By default, inlining of user and library functions (libc) is done. If >> I turn off

There should also be a large notice in 40 point font and bold that says, "gcc4 does not produce byte code by default: you must use the -emit-llvm flag to get LLVM byte code." Erick Tryzelaar wrote: > Hello, > > It looks like the "Getting Started" is missing some info about the gcc > 4.0 frontend. Since it doesn't follow the setup of the cfrontend/gcc3.4 >

Erick Tryzelaar wrote: >> It's a "least surprise" issue. If gcc3 produces bytecode directly, why >> did the gcc4 driver create such a large departure from original, >> expected functionality? It's a rhetorical question, BTW. >> > > I actually know this one :) I believe the powers that be decided that > having a gcc-compatible interface was

On Thu, 24 Aug 2006, Scott Michel wrote: > That's why I would either make sure that the difference is highlighted > in the FAQ and that the difference is highlighted in the "Getting > Started" pages. Otherwise, it'll remain a mailing list FAQ. Patches welcome. Please send a patch, or even just some suggested text, and we'll be happy to include it. Remember that

Thank you for the help. There seem to be several things in my makefiles that are messed up as a result of switching from the gcc3.4 front end to the gcc4 frontend. Is there any documentation listing the things that have changed? Thanks, Ryan Ryan M. Lefever [http://www.ews.uiuc.edu/~lefever] On Fri, 1 Dec 2006, Reid Spencer wrote: > Hi Ryan, > > On Fri, 2006-12-01 at 18:06

I have tested compiling vmkit using gcc3.4 and gcc4.4 Some vmkit files required that I added some explicit typecasts and #includes in order to compile. I have attached my changes against the vmkit svn trunk rev 69439 Using this patch both versions of gcc managed to compiled vmkit on my machine. Cheers Xerxes -------------- next part -------------- An embedded and charset-unspecified text was

I've tried using llvm 2.5 and svn version with both gcc3.4 and gcc-4.3.2. It apparently is not finding the most standard c functions. I suspect this may be because they might live in cygwin.dll. Ins there any to force static linking. Or is there any build recipies that might help? -------------- next part -------------- An HTML attachment was scrubbed... URL: