[llvm-commits] Patch for review: Speeding up ScheduleDAG computations

[Roman Levenstein]

2008/3/5, Dan Gohman <gohman at apple.com>:
> On Mar 4, 2008, at 3:56 AM, Roman Levenstein wrote:
>  >
>
> > make[5]: Entering directory
>  > `/opt/llvm.build/projects/llvm-test/SingleSource/UnitTests/Vector/SSE'
>  > make[5]: *** No rule to make target `Output/sse.expandfft.linked.rbc',
>  > needed by `Output/sse.expandfft.linked.bc'.  Stop.
>
>
> When I've seen this error, the problem has been that my base llvm
>  build configure was run without an llvm-gcc in PATH.  llvm-test
>  apparently relies on the base llvm build to locate llvm-gcc for it.

Thanks! Now I checked again and it seems to work.

So, I have other questions about testing (I guess some of them are
asked quite often ;-):

1) I do run llvm/test tests. At the end I get some figures about the
number of PASSED and UNEXPECTEDLY FAILED tests. This is fine. But is
it guaranteed that UNEXPECTEDLY FAILED are introduced by my code or is
it possible that due to some recent changes to the repository some of
those tests just fail? If it is due to the changes in the repository,
how do I know what are the figures without my changes, so that I can
compare and see new failures introduced by my code? Are those numbers
published anywhere, may be in the nightly tests results??? Or should I
basically have to source trees: one for repository version and one for
my local modifications and then run tests under both trees?

2) If I run the llvm-test tests, how do I produce reports? How do I
know that something failed?

3) How can I run only a selected subset of the tests from llvm-test?
    In particular, I only change LLC mostly. Do I have to run the
llvm-test every time, or can I reduce it to something smaller?

Basically, I have my ScheduleDAG patches ready, All of the proposals
from the review by you and Evan are implemented. But I don't know how
to test them properly using llvm tests and how can I understand if
something is broken by them....

I attach both patches for now, so that someone else can test them as
well, while I'm trying to figure out how to do it on my machine.

-Roman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ScheduleDAGRRList.patch
Type: text/x-diff
Size: 5444 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20080305/45eaecb7/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ScheduleDAGList.patch
Type: text/x-diff
Size: 5508 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20080305/45eaecb7/attachment-0001.patch>