[LLVMdev] hexdump in test cases?

[Rui Ueyama]

On Thu, Oct 2, 2014 at 7:13 PM, Nick Kledzik <kledzik at apple.com> wrote:

>
> On Oct 2, 2014, at 6:52 PM, Rui Ueyama <ruiu at google.com> wrote:
>
>
> I'd do with Python. I'd write a binary-to-text converter as a Python
> script, put it into test/ directory, and then let lit to run the script by
> appending a magic comment to the script like this:
>
>   # RUN: lld -flavor darwin -output %t.binary ...
>   # python %s %t.binary | FileCheck %s
>   #
>   # CHECK: <expected text output here>
>
>
> I know how to make this work on unix based systems.  But, will adding:
>   # RUN: python %s/path/to/hexdump.py %t
> work on Windows?  The lit infrastructure does a lot to make the RUN lines
> work like a very limited shell even on Windows.
>

I didn't actually tried that myself yet, but there are files that contains
'RUN: python' in llvm test directory.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141002/8f4ced14/attachment.html>