-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebase on llvm 16 #421
Rebase on llvm 16 #421
Conversation
(cherry picked from commit 780f90e)
* Remove Windows arm32 packages. Ref: dotnet/runtime#86065 * Remove some windows-arm stuff from llvm.proj (cherry picked from commit c01ca3b)
(cherry picked from commit 13fdf0f)
We have a separate pipeline for it. (cherry picked from commit 673c168)
(cherry picked from commit 43fe12a)
… new --mono-api-version option which returns a numerical version which is used by mono to detect which version of the mono llvm fork it is compiled with. (cherry picked from commit 8d01bed)
…hose associated stack slot index will be saved in MachineFunction, and later can be saved in the mono specific EH tables. (cherry picked from commit d8126bd)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked the ObjWriter part only but it looks okay 👍
I'm merging this so I can start spitting out some packages into a feed to test against. The PR is big enough that nobody's gonna seriously review it, and we can't afford to sit on our hands if we want stuff which depends on LLVM 16, like source-built emsdk, to go in. |
* Rebase our changes on top of llvm release/16.x branch * Don't enable zstd, we can't use it from Brew on arm64 builds on x64 * Build libcxx, and use it instead of libstdc++, on Linux * Remove Windows arm32 packages. Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> Co-authored-by: Zoltan Varga <vargaz@gmail.com>
* Rebase our changes on top of llvm release/16.x branch * Don't enable zstd, we can't use it from Brew on arm64 builds on x64 * Build libcxx, and use it instead of libstdc++, on Linux * Remove Windows arm32 packages. Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> Co-authored-by: Zoltan Varga <vargaz@gmail.com>
* Rebase our changes on top of llvm release/16.x branch * Don't enable zstd, we can't use it from Brew on arm64 builds on x64 * Build libcxx, and use it instead of libstdc++, on Linux * Remove Windows arm32 packages. Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> Co-authored-by: Zoltan Varga <vargaz@gmail.com>
* Rebase our changes on top of llvm release/16.x branch * Don't enable zstd, we can't use it from Brew on arm64 builds on x64 * Build libcxx, and use it instead of libstdc++, on Linux * Remove Windows arm32 packages. Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> Co-authored-by: Zoltan Varga <vargaz@gmail.com>
* Rebase our changes on top of llvm release/16.x branch * Don't enable zstd, we can't use it from Brew on arm64 builds on x64 * Build libcxx, and use it instead of libstdc++, on Linux * Remove Windows arm32 packages. Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> Co-authored-by: Zoltan Varga <vargaz@gmail.com>
* Rebase our changes on top of llvm release/16.x branch * Don't enable zstd, we can't use it from Brew on arm64 builds on x64 * Build libcxx, and use it instead of libstdc++, on Linux * Remove Windows arm32 packages. Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> Co-authored-by: Zoltan Varga <vargaz@gmail.com>
This is a version of #418 without the merge into dotnet/main, which may be easier for reviewers to parse