[PATCH] [prototype] Adding line table debug information to LLVM on Windows
Eric Christopher
echristo at gmail.com
Wed Dec 18 23:17:42 PST 2013
Sorry, missed the question.
Pretty much. Mostly that you could just hand craft the particular
expressions that you're trying to assemble rather than working up an entire
llc -> .o file path. For example the kind of tests done in
test/MC/COFF/secrel-variant.s.
Make sense?
-eric
On Wed Dec 18 2013 at 9:07:40 PM, Timur Iskhodzhanov <timurrrr at google.com>
wrote:
>
> 2013/12/17 Timur Iskhodzhanov <timurrrr at google.com>
>
> > OK, some ideas on how to break this up to make it a bit easier:
> >
> > a) assembler support - the stuff to basically assemble various
> different .s files that happen
> > to have the format. Test cases can be simple .s files and use llvm-mc
> and llvm-readobj to test.
> > At least the label diff doesn't even really need to be a line table I
> wouldn't think.
>
> Can you please clarify what needs to be tested using .s files?
>
> I think you want me to test that
> llc -filetype=asm | llvm-mc -filetype=obj
> generates the same file as
> llc -filetype=obj
> does for the new directives emitted by EmitCOFFSectionReference and
> EmitCOFFStaticOffset (namely ".secrel32" and ".offset from L1 to L2").
>
> Just wanted to double-check that I understood you correctly.
>
>
> ping
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20131219/d04b127e/attachment.html>
More information about the llvm-commits
mailing list