search for: d22753

Displaying 3 results from an estimated 3 matches for "d22753".

Did you mean: d22353
2016 Jul 25
2
[RFC] Make Lanai backend non-experimental
...our *only* rule for a long time has been "keep up or give up". Now, how do we know when a target is good for moving out of experimental? And what is the meaning of experimental anyway? Maybe we should separate the discussion from the actual change. So, if you could comment on the review D22753 about which of the points you'd consider mandatory and which are nice-to-have, that'd probably be easiest. About the Lanai back-end being official, I have no reservations. But I was the only one to say anything, so I'll wait for others to have their say on the review before I put my ap...
2016 Jul 19
3
[RFC] Make Lanai backend non-experimental
> On Jul 19, 2016, at 12:57 PM, Pete Cooper via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Renato >> On Jul 19, 2016, at 9:42 AM, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> A few basic rules to get accepted are if: >> * the target exists and can be easily purchased / emulated
2016 Jul 19
10
[RFC] Make Lanai backend non-experimental
On 19 July 2016 at 17:04, Martin J. O'Riordan via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Presumably if my out-of-tree backend was to be pushed to LLVM, it too would be considered experimental. Yes. Though, not all out-of-tree back-ends end up upstream for different reasons. A few basic rules to get accepted are if: * the target exists and can be easily purchased / emulated