-
Notifications
You must be signed in to change notification settings - Fork 13
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] Snapdragon LLVM Toolchain #15
Comments
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. |
@skganesan do you mind switching times with @tstellar ? Everything ok with your setup? |
I will try again. If not, can you please help showing the slides Nick ?
From: Nick Desaulniers ***@***.***>
Sent: Thursday, September 16, 2021 3:47 PM
To: ClangBuiltLinux/llvm-distributors-conf-2021 ***@***.***>
Cc: Sivakumar Ganesan ***@***.***>; Mention ***@***.***>
Subject: Re: [ClangBuiltLinux/llvm-distributors-conf-2021] [CFP] Snapdragon LLVM Toolchain (#15)
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
@skganesan<https://github.com/skganesan> do you mind switching times with @tstellar<https://github.com/tstellar> ?
Everything ok with your setup?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#15 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVPDBTIZDQMLBG5RG76VLITUCJJS3ANCNFSM5DMDGY7A>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
yes, will do; I can present and you can just say "next slide" and I'll advance them for you. |
Sure. Thank you. I will try sharing and if it does not work, let’s go with that plan.
From: Nick Desaulniers ***@***.***>
Sent: Thursday, September 16, 2021 3:55 PM
To: ClangBuiltLinux/llvm-distributors-conf-2021 ***@***.***>
Cc: Sivakumar Ganesan ***@***.***>; Mention ***@***.***>
Subject: Re: [ClangBuiltLinux/llvm-distributors-conf-2021] [CFP] Snapdragon LLVM Toolchain (#15)
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
yes, will do; I can present and you can just say "next slide" and I'll advance them for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#15 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVPDBTN6PQP27KQVMG5QOGTUCJKSZANCNFSM5DMDGY7A>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Dialed in from phone. Please share the slide as needed and we can get it done.
From: Nick Desaulniers ***@***.***>
Sent: Thursday, September 16, 2021 3:55 PM
To: ClangBuiltLinux/llvm-distributors-conf-2021 ***@***.***>
Cc: Sivakumar Ganesan ***@***.***>; Mention ***@***.***>
Subject: Re: [ClangBuiltLinux/llvm-distributors-conf-2021] [CFP] Snapdragon LLVM Toolchain (#15)
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
yes, will do; I can present and you can just say "next slide" and I'll advance them for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#15 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVPDBTN6PQP27KQVMG5QOGTUCJKSZANCNFSM5DMDGY7A>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Title
Snapdragon LLVM Toolchain
Author
Sivakumar Ganesan, sganesa@quicinc.com, Qualcomm Innovation Center
Distribution
Snapdragon LLVM Compiler Toolchain is distributed for building Android NDK and Bare metal images
Abstract (optional)
Snapdragon LLVM Compiler Toolchain, which is available for Android NDK and Bare metal images, enables use of compilers in a broader range of configurations, providing performance and code size advantage particularly on Qualcomm Snapdragon micro-architectures. Snapdragon LLVM compiler has provided performance gains to a variety of Android applications and libraries.
This talk will discuss on how Snapdragon LLVM compiler manages to stay close to the upstream HEAD and challenges faced during the distribution process
What's unique about the environment you package LLVM for? (optional)
What makes your distribution of LLVM unique? (optional)
We bring upstream patches and merge it in our source tree via automation. The patches are merged out-of-order as we encounter conflicts, build or test issues while bringing in each commit. We use this concept of drain point to bring in all commits till a commit of interest for distribution is merged
What might others learn from your experience? (optional)
There are a wide range of challenges that we face when trying to distribute the toolchain. Some of those challenges include the following issues that are seen with upstream patches:
Another distribution challenge that we encounter is with the LLVM toolchain version that Android AOSP builds come with. New AOSP drops at times use a different LLVM upstream toolchain version resulting in build issues because of mismatch between upstream LLVM compiler and Snapdragon LLVM
What could be improved in upstream LLVM to make working with it easier as a downstream packager? (optional)
Anything that makes the HEAD revision more stable: for instance, enforcing precheckin verification for each commit, means to determine dependent patches etc.
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.
The text was updated successfully, but these errors were encountered: