[LLVMdev] Stack maps no longer experimental in 3.5

[Filip Pizlo]

The only setback is to ensure that we synchronize the renaming with WebKit. 

The WebKit->LLVM interface currently avoids revision-lock; you can take any recent revision of either and build a working browser engine. This is mostly true even when we change the stack map format because of versioning in the format. I'd rather keep it that way. 

Is there a way to do this with intrinsics?  I.e. is there a safe way for WebKit to query whether "llvm.patchpoint" is an available intrinsic, and then fallback to "llvm.experimental.patchpoint" if it's not available?

-Fil


> On Jun 6, 2014, at 11:10 AM, Sean Silva <chisophugis at gmail.com> wrote:
> 
> Hi all,
> 
> It is my understanding that now WebKit depends on the stack map functionality in production. Also, on the mailing lists we've seen lots of users using in this feature. Can we eliminate the experimental status for 3.5?
> 
> Off the top of my head, the changes needed are:
> 
> - A read-through of StackMaps.rst to remove any mention of it being experimental.
> - Removing mention of it being experimental from http://llvm.org/docs/LangRef.html#stack-map-intrinsics
> - Removing the `.experimental` from the name.
> 
> Anything else?
> 
> (also, we'll have to put some stuff in http://llvm.org/docs/ReleaseNotes.html)
> 
> -- Sean Silva
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140606/3b2b5130/attachment.html>