[LLVMdev] RFC: Improving our DWARF (and ELF) emission testing capabilities

Eric Christopher echristo at gmail.com
Mon Feb 4 10:58:38 PST 2013


Ideally for things that are not dwarf you should create a tool similar to
llvm-dwarfdump that is friendly to FileCheck and use that for your
testcases. For things that are dwarf you should use and extend
llvm-dwarfdump.

-eric


On Sun, Feb 3, 2013 at 2:42 PM, Nico Rieck <nico.rieck at gmail.com> wrote:

> On 23.01.2013 00:45, Eli Bendersky wrote:
> > I do mean semantic extraction which provides a representation that's
> > meaningful to a user and hence can be effectively compared in a test.
> > But really, I gave up arguing on this topic a few messages (and heated
> > IRC discussions) ago. RFC retracted.
>
> I actually hit the same predicament for COFF. The few tests that are
> there usually use coff-dump.py whose output is quite limited (many tests
> just compare a binary dump), does not include unwind information, and is
> very different from elf-dump. Then there's llvm-objdump, which does
> resolve relocations and show parts of unwind information. And then
> there's also obj2yaml, but that seems to support even less. And neither
> tool, IMO, produces FileCheck-friendly output.
>
> So even though you retracted your post, I think this issue still stands
> and shouldn't be ignored.
>
> -Nico
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130204/47cd44eb/attachment.html>


More information about the llvm-dev mailing list