[PATCH] reserve constants for Swift bitcode compatibility

[Eric Christopher]

Hi Bob,

I think the calling convention patch is fairly obviously ok. The bar is
usually a little higher for things like attributes and flags, any hope for
a bit more explanation there?

Thanks!

-eric

On Wed, Jul 15, 2015 at 3:57 PM Bob Wilson <bob.wilson at apple.com> wrote:

> As announced at WWDC, we are in the process of open-sourcing the Swift
> compiler. In anticipation of that, I would like to apply the attached patch
> to reserve some constant values to avoid incompatible bitcode between
> Apple’s current Swift compiler and trunk. Swift has a custom calling
> convention that also requires some new flags on arguments and one new
> attribute on alloca instructions. This patch does not include the
> implementation of that calling convention — that will be provided as part
> of the open-source release of Swift; this only reserves the bitcode
> constant values so that they are not used for other purposes on trunk,
> which would make it impossible for people to use bitcode from the Xcode 7
> Swift compiler with the version that we release as open-source.
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150716/e508981f/attachment.html>