Carter, Jack
2011-Dec-07 03:29 UTC
[LLVMdev] Question on test cases for direct object generation
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? Regards, Jack -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111207/d3cef3e6/attachment.html>
Eli Friedman
2011-Dec-07 03:43 UTC
[LLVMdev] Question on test cases for direct object generation
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. -Eli
Jim Grosbach
2011-Dec-07 17:57 UTC
[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
Maybe Matching Threads
- [LLVMdev] Question on test cases for direct object generation
- [LLVMdev] Question on test cases for direct object generation
- [LLVMdev] (MC) Register parsing for AsmParser (standalone assembler)
- [LLVMdev] Using llvm-mc assembler in the llvm test-suite
- [LLVMdev] [MC] [llvm-mc] Getting target specific information to <target>ELFObjectWriter