From llvm-dev at lists.llvm.org Tue Feb 1 08:55:36 2022 From: llvm-dev at lists.llvm.org (Aditya K via llvm-dev) Date: Tue, 1 Feb 2022 16:55:36 +0000 Subject: [llvm-dev] [CFP] Sixth LLVM Performance Workshop at CGO-2022 Message-ID: What: Sixth LLVM Performance Workshop at CGO When: April 3 (Sunday), 2022 Where: Lotte Hotel World, Seoul, South Korea( https://conf.researchr.org/venue/cgo-2022/cgo-2022-venue) Proposals should be submitted to: https://easychair.org/conferences/?conf=llvmcgo2022 The deadline for receiving submissions is: March 01, 2022. Speakers will be notified of acceptance or rejection by: March 07, 2022 Easychair cfp: https://www.easychair.org/cfp/LLVM-CGO-2022 The Sixth LLVM Performance Workshop will be held at CGO 2022 (https://conf.researchr.org/track/cgo-2022/cgo-2022-workshops-and-tutorials). The workshop is co-located with CC, HPCA, and PPoPP. If you are interested in attending the workshop, please register at the CGO website (https://conf.researchr.org/home/cgo-2022). The organizing committee of CGO/PPoPP/HPCA/CC has decided to make the conference in-person this year. The LLVM workshop at CGO will have a hybrid model where both in-person and virtual presentations are welcome. We invite speakers from academia and industry to present their work on the following list of topics (including and not limited to:) improving performance and code-size of applications built by LLVM toolchains. improving performance of LLVM's runtime libraries. improving the security of generated code. any tools or products developed by using one of the libraries in LLVM infrastructure, performance tracking over time, compiler flags, annotations and remarks to understand and improve performance, any other topic related to improving and maintaining the performance and quality of LLVM generated code. While the primary focus of the workshop is on these topics, we welcome any submission related to the LLVM-project, its sub-projects (clang, mlir, lldb, Polly, lld, openmp, pstl, compiler-rt, etc.), as well as their use in industry and academia. We are looking for: keynote speakers (30-60minutes), technical presentations: 30 minutes plus questions and discussion, Tutorials (30-60minutes), BOFs (30-60minutes). Proposals should provide sufficient information for the review committee to be able to judge the quality of the submission. Proposals can be submitted under the form of an extended abstract, full paper, or slides. Accepted presentations can be presented in-person or online. The presentations will be publicly available on https://llvm.org/devmtg/, and recordings will be available on llvm’s youtube channel (https://www.youtube.com/channel/UCv2_41bSAa5Y_8BacJUZfjQ) ---------------------------------------------------------------------------------------------------------------------------- Organizers’ bios and affiliation: ---------------------------------------------------------------------------------------------------------------------------- Johannes Doerfert [Argonne National Laboratory] Johannes is a researcher at Argonne National Laboratory working on compiler optimizations for parallel programs and enhancements to OpenMP to allow more code transformations. Prior organization experience include the EuroLLVM developers meeting in 2017, the LLVM-Performance workshop at CGO in 2018, 2019, 2020 and 2021, as well as LLVM workshop and tutorials at ISC in 2019, 2020 and 2021. Aditya Kumar [Snap Inc.] Aditya is a compiler engineer at Snap Inc. He has been contributing to the LLVM community for the past 9 years and helping organize the LLVM performance workshop for the past 5 years. A tentative list of PC members: ---------------------------------------------------------------------------------------------------------------------------- Johannes Doerfert Argonne National Laboratory Aditya Kumar Snap Inc. Jose M Monsalve Diaz Argonne National Laboratory Shilei Tian Stony Brook University Vaibhav Kurhe Oracle From llvm-dev at lists.llvm.org Tue Feb 1 09:24:47 2022 From: llvm-dev at lists.llvm.org (Tanya Lattner via llvm-dev) Date: Tue, 1 Feb 2022 09:24:47 -0800 Subject: [llvm-dev] Mailman->Discourse Migration on February 1, 10am PST In-Reply-To: References: Message-ID: <595C5D50-D121-42C1-9CC7-C20F46EA34DE@llvm.org> As a reminder, this will be happening this morning. Thanks, Tanya > On Jan 29, 2022, at 8:19 AM, Tanya Lattner wrote: > > LLVM Community, > > As referenced in this blog post , we are getting close to the deadline for migration for some Mailman lists to Discourse. If you are receiving this email from a LLVM Mailman list, then this list will be migrating to Discourse on February 1st. > > We have gone through several test runs and feel that we are ready to do the final migration on February 1st starting at 10 am PST. Once the migration begins, the impacted Mailman lists and Discourse will be read only until it has completed. > > Here are the steps of the migration process on February 1st at 10 am PST: > The Mailman lists that are migrating will be placed in “read-only” mode. No mail will be accepted to the list. > Mailman will be shut down while the final archives are collected. We expect this downtime to be about 15 minutes. > The mailman archives are sent to Discourse for migration (15-20 minutes for data transfer). > The LLVM DIscourse is put into read-only mode. Given the size of our archives, we expect the import to take 5 hours. > Sanity-checks will be made to ensure that everything looks as expected. We estimate this will take 1 hour or less. > The LLVM Discourse will be opened up again with all the archives imported. > We will post on Discourse about how things went and any next steps in the “Announcements” category. > > We will use the Discourse Migration website to communicate where we are in the process. > > We expect the LLVM Discourse to open by 5pm PST, but realize that even in the best plans, there may be unexpected situations that arise that cause the migration to take longer or possibly be stopped. If that occurs, we will evaluate the best course of action and communicate to the community as described above. > > If you have any questions, please let me know. > > Thanks, > Tanya > -------------- next part -------------- An HTML attachment was scrubbed... URL: