search for: bmks

> For each bmk, the undefined symbols are coming from args.c as far as I can > tell. Do I need to link in args.c's bc file for each of them or am I > doing something terribly wrong? These benchmarks were compile a long time ago in a galaxy far far away. In this galaxy, uninitialized globals (int X;) were handled differently, so how these old bytecode files aren't useful anymore.

On Sun, 8 Dec 2002, Chris Lattner wrote: > > For each bmk, the undefined symbols are coming from args.c as far as I can > > tell. Do I need to link in args.c's bc file for each of them or am I > > doing something terribly wrong? > > These benchmarks were compile a long time ago in a galaxy far far away. > In this galaxy, uninitialized globals (int X;) were handled

On Sun, 8 Dec 2002, Chris Lattner wrote: > If you recompile the bytecode files now, (go into each directory and type > 'make final' they should be ok. Perhaps someone can do this and post the > results for everyone to use... I put up what I could compile here: http://tank.cs.uiuc.edu/Olden/ However, I could not get mst to compile: % make final dis: bytecode didn't read

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