[llvm-dev] [RFC] Make Lanai backend non-experimental

Martin J. O'Riordan via llvm-dev llvm-dev at lists.llvm.org
Tue Jul 19 09:04:55 PDT 2016

Oops - meant to send this to the full list.


-----Original Message-----
From: Martin J. O'Riordan [mailto:martin.oriordan at movidius.com] 
Sent: 19 July 2016 15:56
To: 'Krzysztof Parzyszek' <kparzysz at codeaurora.org>
Subject: RE: [llvm-dev] [RFC] Make Lanai backend non-experimental

I know this is a bit of a dumb question, but every so often I read about one back-end or another being made "experimental", or promoted to "non-experimental".

Presumably if my out-of-tree backend was to be pushed to LLVM, it too would be considered experimental.  But what is involved in making a particular target, feature or back-end experimental other than simply agreement?  Are there particular build processes or '-Dmacroname's to add, or how does somebody like me edit my out-of-tree sources so that it would obey the "is experimental" rules?



-----Original Message-----
From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Krzysztof Parzyszek via llvm-dev
Sent: 19 July 2016 15:17
To: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] [RFC] Make Lanai backend non-experimental

On 7/19/2016 6:12 AM, Renato Golin via llvm-dev wrote:
> I don't see why not. LGTM.

Same here.


Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation _______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org

More information about the llvm-dev mailing list