similar to: [LLVMdev] Auto-configuration of llvm/projects directory

On Thu, Sep 23, 2004 at 01:40:46PM -0700, Reid Spencer wrote: > If you use a variable instead of a liberal, you currently get a > warning. What if one uses a conservative instead of a liberal? :) *g, d, r* > The documentation says that this will, eventually, become an error as > it is deprecated because using a variable cannot be successfully > implemented on all platforms. That

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):

> - a "configure"-based build only seems to know about projects/sample/ > and projects/test-suite/, and I couldn't find any way to get it to > build projects/lld/. I investigated a bit more. llvm's autoconf/configure.ac says: dnl Configure all of the projects present in our source tree. While we could dnl just AC_CONFIG_SUBDIRS on the set of directories in projects

I have made few attempts to compile some software packages with llvm. My approach is to define Make variables as follows : export AS=llvm-as export LD=llvm-ld export AR=llvm-ar export CXX=llvm-g++ and then run configure and make. This approach works with very small code bases only. For most of the projects, it bails out with errors. Some of them are very clear, like llvm does not support

2008/12/27 Mark Kromis <greybird at mac.com> > Is this something your planning as putting in the tree, >> thus require pulling in changes from google (license allowing), or does user >> need to have the libraries/headers pre-installed? >> > > Including it in the tree is the most reasonable thing to do. No point in > inconveniencing the user over tiny libraries

On Thu, Mar 30, 2006 at 04:27:55PM +0530, Pratik Mehta wrote: > I have made few attempts to compile some software packages with llvm. > My approach is to define Make variables as follows : > > export AS=llvm-as > export LD=llvm-ld > export AR=llvm-ar > export CXX=llvm-g++ > > and then run configure and make. > > This approach works with very small code bases

Thanks for your valuable input. By the way, I am exporting CC=llvm-gcc and RANLIB=llvm-ranlib for projects that use it. It was a mistake not to write it in the post as apache indeed uses gcc. If you see the error message, you would see llvm-gcc being used. I would try to investigate further on the lines you have mentioned. However, the question that stands is how to best handle failure to compile

Actually, Misha, that won't work. The -C option is used directly in docs/Makefile. So the change will have to go into docs/Makefile. Either that or upgrade install to version 5. Reid. On Thu, 2005-02-17 at 11:33, Misha Brukman wrote: > On Thu, Feb 17, 2005 at 01:21:20PM -0600, Feng Chen wrote: > > llvm[1]: Installing HTML documentation > >

http://wiki.llvm.org/ ? Le 23 mars 09 à 19:04, Bill Wendling a écrit : > So, um...what's the URL for this wiki? > > -bw > > On Mar 23, 2009, at 10:29 AM, Daniel Berlin wrote: > >> Installed it, thanks. >> Seems to work! >> >> 2009/3/23 Misha Brukman <brukman at gmail.com>: >>> On Mon, Mar 23, 2009 at 12:18 PM, Daniel Berlin

Constant *strcon==ConstantArray::get("Value : %d\n"); Sorry Typo. On Tue, 21 Dec 2004, Misha Brukman wrote: > On Tue, Dec 21, 2004 at 03:45:33PM -0700, Sriraman Tallam wrote: > > I have this call instruction to printf inserted which is causing > > an assertion failure. Any pointers to where I am wrong : > > > > Function

On Wed, Jun 23, 2004 at 03:50:09PM -0500, Patrick Meredith wrote: > MetaSplit is an anlysis I just finished writing. It doesn't alter > anything, all it does is build a set of "program instructions". For > some reason even though if I run it with any other combination of > passes I've found, anytime I run it with mem2reg I get a seg fault in > dyn_cast!

Thanks Misha. I tried the "gcc -dM -E /tmp/file.c | grep __sparcv9" but there was no output. Maybe this is the probelm, I do have CXX = g++ -mcpu=v9 CC := gcc -mcpu=v9 in the Makefile.config. Do I need to add -m64 as well? Thanks. Shukang On Thu, 7 Oct 2004, Misha Brukman wrote: > Is your compiler configured to define __sparcv9 when it compiles? > The following should tell

On Fri, 20 Aug 2004 08:52:28 -0700 Reid Spencer <reid at x10sys.com> wrote: > Hi Jeff, > > On Fri, 2004-08-20 at 08:07, Jeff Cohen wrote: > > OK. I've built the front end without any heartaches, but I did > > encountered the following glitches: > > > > The documentation of --with-llvmgccdir is a bit ambiguous. I had to > > try several paths

Hi, After reading Michael Spencer's presentation on lld (http://llvm.org/devmtg/2012-04-12/Slides/Michael_Spencer.pdf), I thought I'd try building it myself. I created projects/lld as a symlink to the lld source tree (is this the right approach?), but I had some trouble getting the llvm build system to actually build it. - a "configure"-based build only seems to know about

On Thu, Feb 17, 2005 at 11:39:27AM -0800, Reid Spencer wrote: > Actually, Misha, that won't work. Sorry, Reid, but I think it will, for the following reason: I don't really know what the -c (lowercase) option does, but install says it's ignored anyway, so that's irrelevant for GNU install. We're talking about the -C option (uppercase). > The -C option is used directly

On Wed, 23 Jun 2004, Patrick Meredith wrote: > What's different about code that's been mem2reg'd from straight front end > code, or anything that mem2reg hasn't been run on? PHINODES! Yup, front-ends generally don't produce SSA form. :) > It appears to be crashing when I try to cast a Value* that's really a > BB* (from the PHInode operands) to a User*,

On Fri, Sep 24, 2004 at 09:38:44AM -0700, Jeff Cohen wrote: > Here's the patch to Signals.cpp. assuming that stdio.h is acceptable > (can't imagine it won't work). We prefer #include <cstdio>, since this is C++ after all. :) -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu

Here's the patch to Signals.cpp. assuming that stdio.h is acceptable (can't imagine it won't work). On Fri, 24 Sep 2004 09:29:05 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > Uh... this may be a silly question, but why can't you include <stdio.h>? > It'd be much better than <iostream>. > > Anyway, I think I'll try this weekend to come

On Fri, Sep 03, 2004 at 03:01:01PM -0500, Anshu Dasgupta wrote: > ><snip> > >for (BasicBlock::iterator I = Dest->begin(); PHINode *PN = > >dyn_cast<PHINode>(I); ++I) > > visitPHINode(*PN); > ><snip> > > > >build_vc71\lib\Transforms\Scalar\SCCP.cpp(202) : error C2275: > >'llvm::PHINode' : illegal use of this type as

I'm CC'ing the llvm-dev list because other people are more knowledgeable about the bytecode format/encoding than I am. Please follow-up the replies to the list. On Wed, Oct 20, 2004 at 11:27:53AM -0700, Yiping Fan wrote: > We also want to extend the llvm instructions/intrinsic > functions/types/passes to support our high-level synthesis for > hardware. First of all, we want to