[llvm-commits] [llvm] r44037 - in /llvm/trunk: include/llvm/CodeGen/ lib/CodeGen/SelectionDAG/ lib/Target/ARM/ lib/Target/Alpha/ lib/Target/IA64/ lib/Target/Mips/ lib/Target/PowerPC/ lib/Target/Sparc/ lib/Target/X86/

[Bill Wendling]

On Nov 12, 2007, at 5:45 PM, Dale Johannesen wrote:

>
> On Nov 12, 2007, at 5:35 PM, Bill Wendling wrote:
>
>> On Nov 12, 2007 5:23 PM, Evan Cheng <evan.cheng at apple.com> wrote:
>>
>>> Also, where are the test case(s)? :-)
>>>
>> I knew someone would ask that. :-)
>>
>> It's hard to come up with a testcase because I need to check multiple
>> lines of output to make sure that the stack pointer isn't modified
>> while a call is taking place. Does anyone know how to do this?
>
> dejagnu is traditionally deficient here (it's hard to test for
> scheduler bugs, too).
> You might do something with grep -n, which prints line numbers, but
> that's fragile
> and I don't know how portable it is.
>
A grep with line numbers was a way I could think to do this also. I  
might be able to hack together a script to check that the stack  
pointer isn't modified during a function call...it would be a bit  
tricky to get correct, though. Maybe I could add something to llvm- 
test that would run successfully only when compiled correctly?

-bw