[docs] Adding target status definition
AbandonedPublic

Authored by rengolin on Jul 25 2016, 6:28 AM.

Details

Reviewers
lattner
Summary

This section of the developer's policy describes the requirements for the targets to become (and remain) as experimental or official back-ends.

I'm avoiding spam, please copy everyone that you feel should see this.

Diff Detail

rengolin retitled this revision from to [docs] Adding target status definition.Jul 25 2016, 6:28 AM
rengolin updated this object.
rengolin set the repository for this revision to rL LLVM.
rengolin added subscribers: llvm-commits, pete, mehdi_amini and 4 others.

PS: "6 months" is an arbitrary time. I'm not hung up on that, but I think we should have "some" time frame...

dschuff added inline comments.
docs/DeveloperPolicy.rst
581

Maybe add "VM or other software implementation" to the list of possible ways a target can exist? "emulator" doesn't quite cover WebAssembly or BPF, for example.

Thanks for writing this up Renato.

I followed up on the original thread as I think some of this is actually setting the bar too high. Want to finish the discussion there first? Or get the non-controversial parts of this in place while that goes on? I have no strong opinions about the most efficacious way to proceed.

lattner requested changes to this revision.Jul 25 2016, 2:50 PM
lattner added a reviewer: lattner.

I think it absolutely makes sense to encode the policy for this into the developer policy document, but think we should converge on the mailing list before discussing specific wording for it.

This revision now requires changes to proceed.Jul 25 2016, 2:50 PM

I think it absolutely makes sense to encode the policy for this into the developer policy document, but think we should converge on the mailing list before discussing specific wording for it.

Works for me.

rengolin abandoned this revision.Jul 25 2016, 3:54 PM