[LLVMdev] Question on test cases for direct object generation

[Carter, Jack]

Thanks for the pointers. I will check out the examples and try a first pass at a Mips test.

Cheers,

Jack
________________________________________
From: Jim Grosbach [grosbach at apple.com]
Sent: Wednesday, December 07, 2011 9:57 AM
To: Eli Friedman
Cc: Carter, Jack; List
Subject: Re: [LLVMdev] Question on test cases for direct object generation

On Dec 6, 2011, at 7:43 PM, Eli Friedman wrote:

> On Tue, Dec 6, 2011 at 7:29 PM, Carter, Jack <jcarter at mips.com> wrote:
>> Is there an official llvm method of creating and submitting test cases that
>> don't affect .s assembly files?
>>
>> When we check in changes that can affect the .s output we submit .ll files
>> with the internalized semicolon instructions on how to check the output .s
>> file.
>>
>> For direct output we currently add to our own test suites that check for
>> correctness. Does the llvm community depend on the individual target owners
>> to do this testing or is there a mechanism for a centralized test?
>
> See test/MC/ELF/ in the LLVM tree.
>

Also test/MC/MachO.

Note that target-specific tests should go into a named target directory underneath (e.g., test/MC/MachO/ARM for ARM tests relying on MachO object file emission).

-Jim