search for: llvmhome

...longs in the repo, IMO it would be nice if you used tdtags as a "template" for this script; there's a large amount of shell-fu (not clever "tricks", but actual "how to make a robust, readable, portable shell script"-fu) in there that you will want to imitate. > LLVMHOME=/home/projects/llvm/upstream/llvm-trunk-build/Release+Asserts/bin > SOPTS="-generate-ppc-fp128" > TOPTS="-mtriple=powerpc64-unknown-linux-gnu -mcpu=pwr7" Hardcoding these seems a bit "wrong". Are there any reasonable defaults we can use? ((pwd, empty, host tripl...

A few people have requested features; I've implemented them in this updated version (attached). Do you think this is worth putting in the repo somewhere? -Hal ----- Original Message ----- > Hi, > > I wrote a small script in order to stress test llc using test cases > generated by llvm-stress. When it finds a case where llc seems to > have crashed, it greps the output for

...plate" for this > script; there's a large amount of shell-fu (not clever "tricks", but > actual "how to make a robust, readable, portable shell script"-fu) > in there that you will want to imitate. Sounds good. I'll look at it. > > > > > LLVMHOME=/home/projects/llvm/upstream/llvm-trunk-build/Release+Asserts/bin > > SOPTS="-generate-ppc-fp128" > > TOPTS="-mtriple=powerpc64-unknown-linux-gnu -mcpu=pwr7" > > > Hardcoding these seems a bit "wrong". Are there any reasonable > defaults we ca...

Hi, I wrote a small script in order to stress test llc using test cases generated by llvm-stress. When it finds a case where llc seems to have crashed, it greps the output for Assertion, LLVM ERROR, etc., removes things that look like hex numbers and ID numbers, and then checksums the resulting text. In this way, it can automatically categorize different bugs into different subdirectories. I