[llvm-commits] [PATCH] TableGen backend support to express relations between instruction

[Sean Silva]

> Thanks. This feature is quite complicated, I think it is best if somebody else reviews the documentation. I want to know if this explanation is understandable by somebody who wasn't involved in the design.

I'll take a look at this later today.

One idea for Jyotsna though: could you break this out into a separate
.rst document, and then link to it?

I briefly looked at your documentation patch and it looks like it
would be more useful/natural to make it more of a "howto". So my
suggestion is to break out the documentation you added to
WritingAnLLVMBackend.html and make a new document
HowToUseInstructionMappings.rst (or whatever name you think is most
appropriate) and then later we can link to it from
WritingAnLLVMBackend.html. To get started, you can just copy
HowToBuildOnARM.rst or HowToAddABuilder.rst and use it as a template
for your work.

Let me know if you need any help with the Sphinx docs. Focus first on
the content since that is the most important. It's easy to clean up
once the content is written.

--Sean Silva

On Mon, Oct 1, 2012 at 12:39 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote:
>
> On Oct 1, 2012, at 8:52 AM, "Jyotsna Verma" <jverma at codeaurora.org> wrote:
>
>> Here is the updated patch which includes a new section into
>> docs/WritingAnLLVMBackend.html and a high-level description of the algorithm
>> in CodeGenMapTable.cpp file.
>
> Thanks. This feature is quite complicated, I think it is best if somebody else reviews the documentation. I want to know if this explanation is understandable by somebody who wasn't involved in the design.
>
> /jakob
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits