Skip to content
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

[CFP] Android's Dream of a Stable Toolchain #9

Open
pirama-arumuga-nainar opened this issue Jul 2, 2021 · 1 comment
Open

[CFP] Android's Dream of a Stable Toolchain #9

pirama-arumuga-nainar opened this issue Jul 2, 2021 · 1 comment

Comments

@pirama-arumuga-nainar
Copy link

Title

Android's Dream of a Stable Toolchain

Author

Pirama Arumuga Nainar, pirama@google.com, Google
Stephen Hines, srhines@google.com, Google (@stephenhines)

Distribution

AOSP LLVM toolchain is used to build the Android platform, the Android kernel and host tools (LLDB server, OpenJDK, adb etc). It also ships with Android Studio and NDK to build native applications.

Abstract (optional)

Our distribution of LLVM supports Linux, MacOS and Windows and uses tools from LLVM ecosystem (lld, compiler-rt builtins, libc++) whenever possible.

In this talk, we'll briefly discuss the distribution (components, build options etc) first and then focus on some operational challenges we face:

  • first-party feature development
  • continuous, nightly, testing
  • managing reverts and cherry-picks
  • cross-testing for Windows

What's unique about the environment you package LLVM for? (optional)

  • Linux, MacOS and Windows toolchains using primarily tools from the LLVM ecosystem.
  • Cross-runtimes (compiler-rt, libunwind, openmp) for Android-supported architectures.
  • Multitude of users (Android platform, kernel, NDK) with varied adoption and support time frames.

What makes your distribution of LLVM unique? (optional)

We don't track an LLVM release but follow LLVM ToT closely. (This also applies to other toolchain maintainers within Google).

What might others learn from your experience? (optional)

What could be improved in upstream LLVM to make working with it easier as a downstream packager? (optional)


Reminder that this is meant to be a 15 minute lightning talk; enough to pique
interests but follow up should be done after. Slides can always include links
to more info; we will ask that you send a PR to this repo with your slides when
they are ready.

@nickdesaulniers
Copy link
Member

Thanks for taking the time to write up a CFP; we'd be overjoyed to have you present at LLVM Distributors Conf 2021! If you still plan on presenting, this is a reminder to get started on your slides for next week. Once they're done, we will contact you about submitting a PDF of your slides as either a pull request to this repository or via email to the organizer. We hope to have a schedule finalized by EOW; we may iterate on the schedule based on whether presenters have conflicts. Please keep this issue open for attendees to ask questions, or close this issue if you no longer plan on attending. Reminder to keep your talk concise (15 minutes); we wont be doing time for questions in order to fit as much content as possible. Attendees should ask questions here in this github issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants