similar to: [LLVMdev] porting glibc

I have a sort of strange request -- I am splitting up a program into multiple threads, which may have duplicated instructions between them. I'd like to run optimizations on the threads separately, but I'd like for the variables common amongst the threads to get register allocated the same way (i.e, a value that is duplicated in the two threads gets mapped to the same register/memory

> Note that compiling glibc with LLVM does not give you a solution to THIS > problem: you'd still have to write a new backend for your ISA. There is > currently a Sparc backend and an X86 backend. Depending on how similar > your architecture is to one or the other, you might be able to leverage > existing code. Take a look at llvm/lib/Target/{Sparc,X86}, though the > X86

When I run with -steens-aa, I get lots of error messages like the following: MergeTypeInfo Folding OrigTy: uint due to:sbyte @ 0! SubType: uint and then it dies with: Assertion failed: Index < Links.size() && "Link index is out of range!", file ../../../include/llvm/Analysis/DSNode.h, line 120 Am I doing something wrong, or is this analysis under development still?

When I try to compile the olden bc's off the webpage I am getting undefined symbols. My compile script works as follows: #!/bin/sh echo "Generating assembly file." llc -f $1.bc echo "Assembling s file." /opt/SUNWspro/bin/cc -xarch=v9 -lm $1.s -o $1 echo "Removing s file." rm $1.s and here is an example of the symbol issues: Undefined first referenced symbol

I must be doing something dumb, but I'm having trouble running the example hello transformation. It is printing "pure virtual method called." All I am doing is checking out a new llvm, compiling it with gmake -k, compiling Hello with gmake, and running: opt -load ../../../lib/Debug/libhello.so -hello < hello.bc > /dev/null where hello.bc is the hello world program. From

On Fri, Mar 07, 2003 at 10:08:23PM -0600, Francesco Spadini wrote: > I noticed that the open projects lists porting glibc to LLVM. I was > wondering if anyone was working on this currently. If no one is on > it, does anyone have an idea of how nasty this would be to do? You'd just have to make glibc compile using llvm-gcc... :) It may need some minor tweaks to be accepted as

I don't follow what you mean - gcc doesn't ignore const and llvm doesn't deviate from gcc nor from the relevant language standards. Note that if you declare a global as const that we do capture this in the ir - what specifically do you want? Please provide an example. -Chris http://nondot.org/sabre http://llvm.org On Aug 14, 2007, at 11:58 PM, "Ryan M. Lefever"

I don't mean to be a pain, but I was thinking about this a bit more. Does gcc ignore the const keyword? If not, why has LLVM chosen to deviate from gcc with respect to the const keyword? If so, then why do we bother using const in LLVM API code? I'm just curious and wanted to understand the thinking behind not preserving const. Thanks, Ryan Chris Lattner wrote: > This property

Does llvm-gcc support the -fPIC option? I am using LLVM on both 32 bit linux and 64 bit linux, if that matters. Regards, Ryan -- Ryan M. Lefever [http://www.crhc.uiuc.edu/~lefever/index.html]

This property isn't preserved on the llvm ir, because const can always be cast away. If you want mod information, then I suggest using the aliasanalysis interface to get mod ref info for a call. -Chris http://nondot.org/sabre http://llvm.org On Aug 8, 2007, at 12:07 AM, "Ryan M. Lefever" <lefever at crhc.uiuc.edu> wrote: > How is c's const keyword translated

This has been reported. http://llvm.org/bugs/show_bug.cgi?id=1317 On 4/10/07, Ryan M. Lefever <lefever at crhc.uiuc.edu> wrote: > > I checked out llvm from cvs & llvm-gcc from svn last night and again > tonight. Each time they compiled and installed fine. After installing > them, I recompiled compiler transforms I had written for opt. opt seems > to load the my

On Wed, Jul 27, 2011 at 3:50 PM, Matt Johnson <johnso87 at crhc.illinois.edu> wrote: > Hi Eli, > > On 07/27/2011 04:59 PM, Eli Friedman wrote: >> >> On Wed, Jul 27, 2011 at 2:28 PM, Matt Johnson >> <johnso87 at crhc.illinois.edu>  wrote: >>> >>> Hi All, >>>     I'm writing a backend for a target which only supports 4-byte,

Hi Eli, On 07/27/2011 04:59 PM, Eli Friedman wrote: > On Wed, Jul 27, 2011 at 2:28 PM, Matt Johnson > <johnso87 at crhc.illinois.edu> wrote: >> Hi All, >> I'm writing a backend for a target which only supports 4-byte, >> 4-byte-aligned loads and stores. I custom-lower all {*EXT}LOAD and >> STORE nodes in TargetISelLowering.cpp to take advantage of

Hi, I think I found a bug. I don't know if it's in upstream gcc or llvm-gcc4. int func() { const int *arr; arr[0] = 1; } $ llvm-gcc main.c -c; echo $? 0 $ gcc main.c -c main.c: In function 'func': main.c:4: error: assignment of read-only location The difference disappears when arr[0] is replaced by *arr. (I tried the above with gcc 4.1.2, 3.4.6, 4.0.3. (I don't

LLVM, What do I pass into the DSG in order to access the globals vector of functions that a function pointer may be calling. The code: CallInst *calli = dynamic_cast<CallInst*>(*i); std::vector<GlobalValue*> funcVect = theGraph.getNodeForValue(calli->getCalledFunction()).getNode()->getGlobals(); Doesn't appear to work... getCalledFunction() returns 0 Dave On Fri, 6 Dec

On Tue, Jun 24, 2008 at 2:03 AM, Ryan M. Lefever <lefever at crhc.uiuc.edu> wrote: > My problem is that if I use the -g option in lines 1 and 2, then when I > run llvm-ld in line 5, it complains that there are undefined references > to .LlableX. -g + optimization is unsupported at the moment. Off the top of my head, I know that global DCE and inlining break debug info; probably

Yup! -bw On Nov 3, 2008, at 7:39 PM, Ryan M. Lefever wrote: > Does llvm-gcc support the -fPIC option? I am using LLVM on both 32 > bit > linux and 64 bit linux, if that matters. > > Regards, > Ryan > > -- > Ryan M. Lefever [http://www.crhc.uiuc.edu/~lefever/index.html] > _______________________________________________ > LLVM Developers mailing list >

I use the following code to do the depth first search on the DSGraph. And I always got this error message. Couldn't figure out what's wrong. Could you please let me know? Besides, I really have no idea about what those functions do. Is there any documentation about DSGraph functions besides the pool allocation paper? Thanks, xiaodong Code: for( df_iterator<DSNode*> I =

On Fri, 29 Nov 2002, Anand Shukla wrote: > There is a pass "UnifyFunctionExitNodes()" (you can add it to AnalysisUsage > of your pass) that does the trick. Yup, just like Anand says, this pass will make it so that there is at most one exit node from the function, which you can use for your analysis (it will even tell you which BB that is too). Note that a function may _not_ have

This certainly doesn't occur in gcc mainline. In fact, I improved the error message, and added a error test to gcc just yesterday. On 8/9/07, Chris Lattner <sabre at nondot.org> wrote: > On Wed, 8 Aug 2007, Nikhil A. Patil wrote: > > I think I found a bug. I don't know if it's in upstream gcc or llvm-gcc4. > > Looks like a bug, please file a bugzilla entry. >