August 2026 - Woa-wg - lists.corecollective.dev

Notes: 2026-08-25 CoreCollective Windows on Arm Technical
by Nathalie Chan King Choy (Windows on Arm) 26 Aug '26

26 Aug '26

Hi all, Sorry about the abrupt end to the call. I thought I had clicked the "reclaim host" button when I joined the call, but apparently it did not work & Grant was still assigned as alternate host, so Zoom took the call down when he left. 😅 The notes from this week's call are below. Please let us know if you spot any errors or important omissions. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups Next OOO: Sep 9-11 *Attended:* Anthony R. Carlos S. Dave W. Evgeny K. Gleb K. Grant L. John S. Julianus Kiran C. Leandro L. Marcus P. Mayank A. Mike H. Nathalie CKC Omair J. Paul B. Rajath H. Rick D. Saket J. Thomas D. Tyler M. *Links shared in chat:* - From Kiran: https://packages.msys2.org/base/mingw-w64-flang - From Mayank: - https://github.com/openai/tiktoken/pull/501 - https://github.com/pytorch/pytorch/pull/194563 - https://github.com/Multicorewareinc/tensorflow - https://github.com/tensorflow/tensorflow/pull/124329 - From Gleb: - https://github.com/confluentinc/confluent-kafka-python/pull/2190 *AI Notes - please notify us of inaccuracies:* Meeting Overview - Discussed compiler support for Fortran and GNU toolchain integration on Windows on Arm, focusing on Flang, GFortran, and MSYS2 compatibility. - Reviewed Python package enablement progress on Windows on Arm, including PyArrow ABI3 migration, PyTorch performance optimizations, TensorFlow external releases, and CI runner availability in Azure DevOps. - Received technical updates on GCC upstreaming efforts, SEH (Structured Exception Handling) patches, native Bash execution for Git for Windows, and LLVM release and PGO build performance. Decisions/Key Takeaways - MulticoreWare created a fork and published a beta release of TensorFlow for Windows Arm64 in their external repository while upstream review continues. - SEH support for Binutils has been successfully upstreamed, with the final GCC SEH patch currently undergoing upstream review. - [Deferred] Decision on whether to prioritize Flang GNU-compatibility changes versus GFortran development for Windows on Arm deferred pending further community input and testing results. Action Items - *Gleb K.* - Provide context to Anthony on PyArrow ABI3 migration PRs discussion - *Anthony R.* - - Review PyArrow ABI3 migration PRs and context provided by Gleb K. - *Evgeny K.* - Prepare a summary of cross-compilation test results for Fortran on Linux for the next meeting. - *Marcus P.* - Follow up on Azure DevOps Arm runner availability and free-tier support plans for open-source projects. - Follow up with Michael regarding the status of PyTorch releases on PyPI. - Follow up offline with Omair on processing power for LLVM builds - *Mayank A.* - Check team's status on confluent-kafka-python signature process issue and report back. - Discuss setting up weekly builds and tests for TensorFlow with Gaurav. - Make the PR for Open3D (instead of having Ke do it) and reach out to WoA list once the PR is created. - *Nathalie C.* - Set up CoreCollective Hub accounts for Rajath H. and Annamalai C. by later this week. - *Rajath H.* - Follow up offline with Gleb K. regarding the required NVIDIA Python and CUDA package list. - Assist in finding an OpenAI contact for the tiktoken PR. For Future - Evgeny K. scheduled to present a summary of Fortran cross-compilation test results at the next meeting. - Cryptography release with Windows on Arm support scheduled for September. Notes *Fortran and Flang Toolchain for Windows on Arm* - Fortran on Windows on Arm currently lacks a GNU-style compatible compiler, restricting the execution of the GFortran test suite, R tools, and GNU-dependent libraries. - Current Flang implementations are compatible with MSVC ABI, leading to integration issues when building libraries like OpenBLAS and LAPACK that rely on GNU-style infrastructure. - Two potential solutions under evaluation include updating Flang driver/linker directives for GNU library compatibility or developing GFortran for Windows on Arm. - MSYS2 currently contains downstream packages for Flang on Arm64; Kiran recommended reviewing these downstream patches for upstreaming opportunities. - Upstream GCC work has made progress with SEH integrated into Binutils, enabling native toolchain builds once the final GCC patch is accepted. *Python Package Enablement and CI Infrastructure* - PyArrow maintainers require an ABI3 migration to reduce wheel build output and CI storage load before accepting the Windows on Arm support PR. - Anaconda's roadmap indicates that conda and Miniconda support for Windows on Arm is not expected to be completed before October. - MulticoreWare submitted performance optimization PRs for PyTorch on Windows Arm64 and published a beta release of TensorFlow based on their fork. - Tiktoken PR #501 for Windows Arm64 support has been submitted to OpenAI, with outreach ongoing to connect with OpenAI maintainers. NVidia will join in helping to find an OpenAI Tiktoken contact. - Azure plans to expand Arm runner support, but matching the free tier is not currently on their roadmap & that will be a blocker for open-source projects - Cryptography release for Windows on Arm is targeted for September - Confluent-kafka-python PR #2190 signature process is under review following initial technical issues. *GCC, LLVM, and System Utilities* - Native Bash execution under MSYS2 was successfully cross-compiled and tested internally by MulticoreWare, demonstrating 3x to 5x performance improvements over emulation. - Pull requests for Git for Windows integration with native Bash are currently under review by maintainers & QC to address feedback - LLVM 23 release is expected imminently from upstream. - LLVM release build testing using ThinLTO, PGO, and PDB generation on a 16-core Arm machine required 6 hours and 45 minutes, prompting discussions on increasing GitHub runner resources. -- You received this message because you are subscribed to the Google Groups "CoreCollective Windows on Arm" group. To unsubscribe from this group and stop receiving emails from it, send an email to windows-on-arm+unsubscribe(a)corecollective.dev. To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/windows-on-arm/CAJ-K….

2 1

[CoreCollective Edge] [CoreCollective Members] CoreCollective Causeway migration and website update
by Grant Likely (Edge Compute) 21 Aug '26

21 Aug '26

Hi CoreCollective members, A couple of quick updates before the weekend: First, the move to Causeway for workgroup management is just about finished. All of you either now have a Causeway account set up, or an email invite to create an account. Look for an email from hub.corecollective.dev if you missed it. We’ll cutover to the new lists shortly, and we’ll provide some details about what we can do with the new forum. Second, we’ve updated the website to provide landing pages for each of the groups. Now when the tile for the working group is clicked on, it will take you to an info page rather than the bare mailing list archive. Take a look at https://corecollective.dev/working-groups. Content on the pages will get fleshed out in the coming weeks to reflect what is happening in each group so that you can use it to highlight the collaboration that is happening in each group. If there is anything specific you’d like to see in a working group page, the community managers, Don, Nathalie and Julianus can help get it added. Thanks, Grant --- Grant Likely CoreCollective Technical Chair IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- You received this message because you are subscribed to the Google Groups "CoreCollective Members" group. To unsubscribe from this group and stop receiving emails from it, send an email to members+unsubscribe(a)corecollective.dev. To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/members/AM0PR08MB112….

1 0

Causeway migration of CoreCollective Windows on Arm WG
by Nathalie Chan King Choy (Windows on Arm) 20 Aug '26

20 Aug '26

Hi, Heads up: I’m migrating the CoreCollective Windows on Arm list over to Causeway at hub.corecollective.dev today./ You may see some emails about account creation and subscriptions. All of them should be from hub.corecollective.dev. Once I’m done I’ll send another email to test the new setup. Best regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups -- You received this message because you are subscribed to the Google Groups "CoreCollective Windows on Arm" group. To unsubscribe from this group and stop receiving emails from it, send an email to windows-on-arm+unsubscribe(a)corecollective.dev. To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/windows-on-arm/CAJ-K….

1 1

PyArrow abi3 support
by 'Gleb Khmyznikov' via CoreCollective Windows on Arm (Windows on Arm) 20 Aug '26

20 Aug '26

[Python][Packaging] Support abi3 wheels for pyarrow · Issue #50398 · apache/arrow<https://github.com/apache/arrow/issues/50398> Good day Omair and Anthony. There's a good opportunity to contribute into pyarrow, they need to have the abi3 support to be done before they can include WoA support. This work related to changes in pyarrow itself + perf testing (even with the perf degradation they are fine to have the abi3 anyway). Could you explore how big is this scope and if it possible to invest our resources into that. QC partner made this PR<https://github.com/apache/arrow/pull/48539> but it blocked until abi3. There's some signals from nv as well... -- You received this message because you are subscribed to the Google Groups "CoreCollective Windows on Arm" group. To unsubscribe from this group and stop receiving emails from it, send an email to windows-on-arm+unsubscribe(a)corecollective.dev. To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/windows-on-arm/CH4PR….

2 1

Notes: 2026-08-10 CoreCollective Windows on Arm Technical
by Nathalie Chan King Choy (Windows on Arm) 12 Aug '26

12 Aug '26

Hi all, The notes from this week's call are below. Please let us know if you spot any errors or important omissions. *Also, let me know if you have folks you'd like to forward the invite for 8/25 to regarding this Flang topic:* *"Windows on Arm lacks a GNU-compatible Fortran compiler. LLVM Flang (flang-new) is currently our only options, but it only targets the MSVC ABI rather than the GNU/mingw ABI that much of the scientific and numeric open-source ecosystems rely on for Windows (e.g., BLAS/LAPACK and MinGW-w64/Rtools-style toolchains).We have two primary paths forward:1) Bring up native gfortran on aarch64-w64-mingw32. This would achieve full parity with x64, but it depends on upstreaming GCC's C++, SEH, and native compilation work.2) Extend LLVM Flang to support the GNU ABI for Windows on Arm.These approaches are not mutually exclusive, and we may pursue both.We would like to gather the Flang community, toolchain vendors, and other stakeholders to properly scope the effort, map out dependencies for each path, identify who is currently blocked, and align on the best strategy moving forward."* Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups *Attended:* Don H. Evgeny K. Gleb K. Grant L. Jillian B. Marcus P. Nathalie C. Omair J. Rick D. Saket J. Thomas D. Tyler M. *Shared in chat:* - https://omjavaid.github.io/wheels-on-arm/ - In Gleb's but not Omair's list: memray, oss2 - Evgeny's update on GCC: - Upstreaming auto-import support for dynamic linking, which is important for the native toolchain. - Removing unnecessary scripts before making the repository for weekly Windows builds public. *AI Notes - please notify us of inaccuracies:* Meeting Overview - Welcome and introduction of new Arm participant Rick D. and Linaro staffing update. - Python ecosystem enablement, package tracker, Python 3.15 release status, and at-risk package identification. - Debugger maintenance (GDB/LLDB), LLVM performance optimization (PGO/ThinLTO), GCC updates, and repository management. Decisions/Key Takeaways - [Deferred] GDB maintenance and testing on Windows on Arm is deprioritized and added to the backlog due to resource constraints and available alternatives (WinDbg, MSVC, LLDB). - Python 3.15 on Windows on Arm meets minimum release requirements and is on track for an October launch. - Should try to transition non-engineering maintainer engagement for Python packages to scale teams (App Assure and AppReady). Action Items - *[Gleb K.]* - Work with Omair J. to consolidate Python package tracking lists and identify critical path items. - Compile a shortlist of red-list at-risk packages (e.g., PyArrow, gRPCIO, CRC32) needing priority intervention. - *[Marcus P.]* - Connect with Rick D. to discuss engaging App Assure and AppReady teams for Python package maintainer outreach. - Follow up offline with Omair J. on LLVM PGO and ThinLTO performance upstreaming strategy and funding. - Coordinate cross-company marketing efforts (Microsoft, Arm, Qualcomm, Nvidia) for the Python on Windows on Arm release. - *[Nathalie C.]* - Distribute the prioritized project backlog list by email for offline review. - (DONE) Add Thomas D. as a collaborator the CoreCollective Windows on Arm GitHub repository upon receiving his GitHub ID. - (DONE - See email text above) Include Omair J.'s Flang integration write-up in the meeting notes and send a separate calendar invite for the next meeting. - *[Omair J.]* - Work with Gleb K. to merge Python package tracking data into a unified list. - Follow up offline with Marcus P. regarding LLVM PGO and ThinLTO testing and upstreaming. - *[Rick D.]* - Meet with Marcus P. to explore using App Assure and AppReady for package maintainer communication. - *[Thomas D.]* - Review the list of buildable Python packages to identify opportunities to accelerate enablement. - (DONE) Provide GitHub ID to Nathalie C. to receive collaborator access to the CoreCollective WoA WG repository. - Investigate potential team connections with Open3D. For Future - Discuss Flang integration during the initial portion of the next meeting. Notes - *[Team Updates & Introductions]* - Rick D. is on Arm's strategic developer and ecosystems team, Before that, he worked at Microsoft and GitHub. He is in WoA WG to focus on Python ecosystem partnerships. - Maxim Kuvyrkov has left Linaro; Windows on Arm technical topics will be managed by Omair J. and Mike H. - *[Python Ecosystem & Package Trackers]* - Omair J. created a "Wheels on Arm" GitHub tracker <https://omjavaid.github.io/wheels-on-arm/> analyzing top packages, filtering pure vs. native Python, and applying a priority algorithm based on download count, AI/ML focus, and multi-platform availability. - Omair J. suggested submitting direct PRs for buildable packages beyond the top 1,000 during the remaining ~4 weeks prior to launch. - Gleb K. analyzed the second 1,000 packages for installability and source buildability, highlighting packages memray and oss2 that are not in Omair's list - Non-engineering outreach (maintainer communication and CI PRs) coudl be done by scale teams like App Assure and AppReady. - Steve Dower confirmed Python 3.15 for Windows on Arm is green for release, meeting minimum requirements with CI in place, targeting an October launch. - Cryptography support is restored in PR form and expected in the September release. - Gleb K. identified PyArrow, grpcio, and CRC32 as key at-risk/red-list packages needing priority focus. - *[Debuggers (GDB & LLDB)]* - GDB for Windows on Arm received initial upstream contributions in January, but Linaro is not currently testing or maintaining it. - WinDbg and MSVC debuggers remain viable alternatives for debugging on WoA. - LLDB is functional on Windows on Arm, but additional upstream maintenance and review resources are needed for new features like SVE and SME. - *[LLVM Performance (PGO & ThinLTO)]* - Marcus did a rough unofficial test applying PGO dataset from Linux and ThinLTO to Windows on Arm: LLVM builds demonstrated a 10-15% performance improvement. - Enabling ThinLTO within standard LLVM build constraints requires a more capable runner image to complete within 6 hours. - Linaro is preparing a report on Clang versus LLVM performance analysis as a follow-up to a presentation with Saket. - *[GCC Updates & External Queries]* - Arm is upstreaming auto-import support for dynamic linking to support native toolchains and preparing the repository for public weekly Windows builds. - Multiple external partners have expressed interest in GCC builds for Windows on Arm to Microsoft. - The team will inquire with AppReady and internal relationship teams regarding potential connections to Open3D. - *[Repository Governance & Administration]* - Nathalie C. is adding external collaborators the CoreCollective Windows on Arm WG repository. Let her know if the current permissions granted are not sufficient. - Project backlog prioritization list will be circulated via email for offline review. -- You received this message because you are subscribed to the Google Groups "CoreCollective Windows on Arm" group. To unsubscribe from this group and stop receiving emails from it, send an email to windows-on-arm+unsubscribe(a)corecollective.dev. To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/windows-on-arm/CAJ-K….

1 1

Agenda: 2026-08-11 CoreCollective Windows on Arm Technical (Daylight Savings)
by Nathalie Chan King Choy (Windows on Arm) 10 Aug '26

10 Aug '26

Hi all, Here are the topics that I have collected so far for 2026-08-11: - Python - Omair: list of critical Python packages situated outside the top 1,000 ranking - Result of blocked package bucketization call - Could someone give an update about latest status on GDB? - GCC - Performance/LLVM - Enablement - Review backlog to see if anyone is working on some of the items - Governance for CC WoA WG repo now that we’re adding more ppl: What criteria for the different levels? Please let us know if you have additional topics. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups -- You received this message because you are subscribed to the Google Groups "CoreCollective Windows on Arm" group. To unsubscribe from this group and stop receiving emails from it, send an email to windows-on-arm+unsubscribe(a)corecollective.dev. To view this discussion visit https://groups.google.com/a/corecollective.dev/d/msgid/windows-on-arm/CAJ-K….

1 0

Fwd: Notes: 2026-07-28 CoreCollective Windows on Arm Technical
by Nathalie Chan King Choy (Windows on Arm) 10 Aug '26

10 Aug '26

---------- Forwarded message --------- From: "Nathalie Chan King Choy (Windows on Arm)" <woa(a)hub.corecollective.dev> Date: Thursday, 30 July 2026 at 11:00:25 UTC-7 Subject: Fwd: [CoreCollective WoA] Notes: 2026-07-28 CoreCollective Windows on Arm Technical To: CoreCollective Windows on Arm Hi all, The notes from this week's call are below. Please let us know if you spot any errors or important omissions. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups *Attended:* Anthony Dave W. Evgeny K. Gleb K. John S. Marcus Mayank A. Nathalie CKC Omair J. Paul B. Randy L. Tamas P. Thomas D. Tyler M. *Links shared in chat:* - https://github.com/khmyznikov/PyEnv-WoA-State/issues/50# issue-5000192882 got a first issue from community ☺️ - https://github.com/StrawberryPerl/spbuild/issues/ 20#issuecomment-3206756096 - https://github.com/msys2/msys2-runtime/pull/344 - https://github.com/lazka *AI Notes - please notify us of inaccuracies:* Meeting Overview - Maintainership and collaborative support tracking structures for ecosystem libraries on Windows on Arm. - Path to remove the Python experimental designation. - Toolchain progression, patch submittals, and runtime compatibility blocks across Strawberry Perl, GCC, MSYS2, PyTorch, and TensorFlow. Decisions/Key Takeaways - The Windows Arm Working Group GitHub repository is where we are planning to track community issues and manage library maintainership discussions, rather than a WoA maintainer mailing list. - Technical representatives from Arm, Qualcomm & Microsoft will join the working group GitHub repository to increase visible team. - Priority order: completing the native compiler toolchain and upstreaming Cygwin target changes to binutils ahead of active Strawberry Perl distribution enablement. - [Deferred] Categorizing remaining blocked packages into localized maintainer strategic groups was deferred to an upcoming offline breakout working call due to session time constraints. - TensorFlow will be delivered as a localized snapshot release through a partner repository. Action ItemsDave W. - Discuss internally at Arm to identify technical resources who will join the working group repository as external collaborators & send their GitHub IDs to Nathalie. - Confirm with Chris if ACL functions are actively being folded directly into an alternative library & let Marcus know. Evgeny K. - Arm to submit the dynamic link library relocation patch to unblock upstream native toolchain compilation by end of day today. - Contact Johannes directly & try to understand reason for review delays surrounding the MSYS2 CI pull request from Qualcomm. Gleb K. - Present the Windows Arm Working Group GitHub repository option to the PyArrow mailing list for community discussion Marcus - Engage Steve Dower by the end of this week to confirm ecosystem package requirements and baseline milestones for removing the Python experimental tag, check if we have priority inversions (dependencies on non-top-1000 packages), and pointers to community members who could represent verticals for testing - Contact Tucker Burns about PyTorch CI status and resourcing limits for making Windows on Arm wheels from nightlies, investigating issues, etc. Mayank A. - Gather and forward Qualcomm engineer GitHub accounts to Nathalie CKC to add as external collaborators to WoA Technical WG GitHub repo - Contact Christoph Reiter (Lazka) directly to secure review engagement on the pending MSYS2 runtime pull request Nathalie CKC - Issue external collaborator invitations to repository joiners upon receipt of developer GitHub identifiers (see chat for Marcus') - Coordinate and schedule an offline breakout call with Mayank A., Gleb K., and Anthony to bucketize remaining blocked packages. Omair J. - Present list of critical Python packages situated outside the top 1,000 ranking during the next group assembly. Paul B. - Investigate internal channels at Arm to determine why official ACL wheel distributions for Windows Arm64 stopped after August 2025. For Future - Complete the upstreaming of Cygwin target modifications to binutils during the current calendar year before the submission window closes at the end of November. - Allocate technical resources later this year to establish a benchmarking workflow and perform detailed GCC performance evaluation against LLVM and MSVC. Connect Evgeny's team with the Microsoft engineers who have been running spec tests. NotesPyArrow & GitHub Working Group Support Structure - Upstream project maintainers require dedicated, interactive support to troubleshoot Windows on Arm test regressions and prevent them from blocking primary framework releases. Upstream maintainers explicitly declined physical hardware donations due to corporate funding limitations governing external project labor. - Relying on an individual named maintainer poses a continuity risk because current project funding is only secured through later this year. Implementing a shared team-based responsibility model via a joint repository reduces the project bus factor. - The repository currently lists only two active contributors, prompting a push for expanded technical representation from Microsoft, Arm, and Qualcomm engineers. Python Experimental Status & Package coverage - Steve Dower retains gatekeeping authority over Windows Python binaries, applying subjective validation metrics centered on overall community sentiment and successful basic script execution during the opening 10 minutes of operation. - Compatibility tracking indicates that 95% of the top 1,000 most downloaded packages run successfully on native targets. The group's primary objective is to prevent workflow breaks when native execution becomes the platform default. Need to get some testing done on verticals. - Relying solely on download lists risks missing low-level dependencies or rapid-iteration frameworks in emerging sectors like AI that lack high download volume. - Extracting architecture-specific package download metrics is highly limited because command-line tools and user agents systematically mask or omit native Windows on Arm silicon descriptors. Toolchain and Strawberry Perl Blockers - Strawberry Perl acts as the primary default Perl implementation on Windows, causing widespread build blockages because package managers like Conan structurally reject mixed-architecture pipelines even though emulated x64 Perl executes cleanly for build utilities like OpenSSL. - A Microsoft partner currently implements an emulated execution strategy for internal workloads, incurring significant resource overhead from double-jitting operations that translate X86 instructions while compiling Perl scripts to machine blocks. - Compiling the basic runtime environment is achievable through standard cross-compilation frameworks, whereas generating the full package distribution requires a completely integrated native toolchain. - A severe P1 compiler regression affecting MinGW target builds across both X64 and Arm64 architectures was successfully isolated, resolved, and integrated upstream. MSYS2 and Git for Windows Status - Internal validation confirms that the MSYS2 runtime and core Git for Windows systems function correctly, but upstream integration remains stalled due to a lack of review engagement on an X64 CI pull request. - Qualcomm's internal tracking shows 289 executed validation tests with only 3 or 4 failures stemming from POSIX spawn updates and underlying GCC behaviors. Machine Learning Runtimes (PyTorch, ACL, TensorFlow) - PyTorch optimization continues via nightly builds; standard release wheel deployments are delayed because engineering resources are unavailable to troubleshoot downstream production pipeline failures. - Official ACL wheel updates for Windows Arm64 have been fully halted since August 2025 due to baseline MSVC integration limitations created by internal inline assembly blocks. - TensorFlow compilation has been achieved internally, successfully resolving 500 to 600 validation passes out of approximately 3,000 test cases; current frictional boundaries are limited to Google dependencies like gRPC IO.

1 0

Fwd: Notes: 2026-07-14 CoreCollective Windows on Arm Technical
by Nathalie Chan King Choy (Windows on Arm) 10 Aug '26

10 Aug '26

---------- Forwarded message --------- From: "Nathalie Chan King Choy (Windows on Arm)" <woa(a)hub.corecollective.dev> Date: Monday, 20 July 2026 at 07:50:40 UTC-7 Subject: Fwd: [CoreCollective WoA] Notes: 2026-07-14 CoreCollective Windows on Arm Technical on Arm Technical To: Nathalie Chan King Choy (CoreCollective) Cc: CoreCollective Windows on Arm Clarification for following, as far as I can remember: - Omair J. please reply to this message with the first part of your LLVM update, Zoom transcription captured it as “the ROM-side billboards will be moved down to New York” which I am guessing not correct." "Windows on Arm buildbots will be moved to new servers in Linaro Lab" Thanks! -- Omair Javaid www.linaro.org On Wed, 15 Jul 2026 at 20:18, Nathalie Chan King Choy wrote: Hi all, The notes from this week's call are below. Please let us know if you spot any errors or important omissions. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups *Attended:* Gleb K Grant L Jillian B John S Mayank A Nathalie C Omair J Randy L Saket J Thomas D Tyler M *AI Notes - please notify us of inaccuracies:* Meeting Overview - The meeting focused on tracking the enablement of Python packages for Windows on Arm, specifically discussing the strategy for managing the package tracker and addressing unresponsive maintainers. - The team reviewed platform readiness criteria for a regular, non-experimental release and addressed current progress on major blockers like PyTorch and TikToken. - Attendees discussed upcoming RCs for LLVM release Key Decisions Made - [Deferred] The discussion regarding the three package buckets was postponed to two weeks from now due to Anthony being OOO. Mayank & Gleb will be able to attend in 2 weeks. - The team decided to create an additional list or table to track newly enabled packages that fall outside the main tracker's top-1000 parameters. - Wednesday’s WoA Steering Committee call will be canceled if no topics are submitted within the next few hours. Action Items - Omair J. - Omair J. please reply to this message with the first part of your LLVM update, Zoom transcription captured it as “the ROM-side billboards will be moved down to New York” which I am guessing not correct. - Gleb K. - Review the three package buckets once shared and perform preliminary analysis prior to the next meeting. - Mayank A. - Assist with categorizing and segregating the Python package buckets by identifying unresponsive or review-blocked maintainers. - Nathalie C. - Search for an email from Anthony identifying unresponsive package maintainers to assist with bucket categorization. - Distribute the meeting notes. - Include the package buckets to categorize maintainer blockers in the meeting notes. Here they are: - Non-responsive - Does not understand the case - Understands the case but is not interested. For Future - Discussion on package buckets is scheduled to occur in two weeks at next WoA technical call. - The LLVM 23 RCs are expected in a few weeks. Notes Python Package Tracker Strategy - Omair J. suggested expanding the Python package tracking list to include easily buildable packages that natively support Windows on Arm. - Gleb K. explained that the current tracker is primarily based on the top 1,000 downloaded packages, with roughly 10 partner-requested additions. - The team discussed that adding numerous new packages immediately might make progress look stagnant on paper, though expanding the overall enabled count remains highly beneficial. - The new packages aiohttp, safetensors, and ijson have been released on PyPi. - Gleb K. noted in the chat that the list of tracked packages will likely be complete once conda lands. Platform Readiness Assessment - Saket J. noted that Steve Dower at Microsoft is responsible for the Python release and is looking for a general sense of platform readiness rather than a target number of enabled packages. - The WoA Python package readiness is currently estimated to be at 95% plus. - Saket J. recommended reaching out directly to Steve Dower to get his current perspective on the platform's state. Blocker Mitigation and Partner Engagement - PyTorch: Gleb K. found contacts on the Meta side to help coordinate, noting that Microsoft's internal team has been moved off this effort. - TikToken: Gleb K. identified a contact who may be able to reach out to OpenAI. - Anaconda: Gleb K. identified the internal team member coordinating with Anaconda to help align on prioritized blocked packages from the top-1000 list once Anaconda’s infrastructure work is complete. - Large Code Issue: Gleb K. is attempting to track down owners for the issue shared by Omair J. in a previous call and is consulting individuals at Arm for support but not making progress there. - Arm Community Relations: For some of the cases where the maintainer doesn’t understand the value of the WoA patches, Tyler M. clarified that Arm can handle open-source relationship issues on a case-by-case basis via internal contacts and does not require bringing external participants into a WoA technical call. Package Bucketization - Nathalie C. shared the three package buckets in the chat: "Non-responsive", "Does not understand the case", and "Understands the case but is not interested". - Mayank A. confirmed that most of the blocked items previously shared on the CoreCollective WoA mailing list are Python packages and agreed to assist in segregating them into these categories. LLVM Update - The LLVM 23 RCs are expected to release in a couple of weeks, with the Windows 11 release targeted around September 1st.

1 0

Fwd: Status of MinGW & GCC blockers for Strawberry Perl enablement?
by Nathalie Chan King Choy (Windows on Arm) 10 Aug '26

10 Aug '26

---------- Forwarded message --------- From: "Nathalie Chan King Choy (Windows on Arm)" <woa(a)hub.corecollective.dev> Date: Monday, 13 July 2026 at 10:26:14 UTC-7 Subject: Fwd: [CoreCollective WoA] Status of MinGW & GCC blockers for Strawberry Perl enablement? Strawberry Perl enablement? To: Evgeny Karpov (Arm) Cc: CoreCollective Windows on Arm Hi Evgeny, Regarding Strawberry Perl dependency on GCC & MinGW, the legacy Linaro WoA working group tracking spreadsheet I received points to this discussion: https://github.com/StrawberryPerl/spbuild/issues/20#issuecomment-3206756096 Thanks for the GCC update for tomorrow's call. Best regards, Nathalie On Mon, 13 Jul 2026 at 09:11, Evgeny Karpov wrote: Hi Nathalie, Thank you for reaching out. I will look into the Strawberry Perl issue. Could you please share more details about the blockers? I will not be able to attend tomorrow's meeting. GCC update is below: - A patch to fix the regression in the mingw repo has been merged upstream. - A regression in the gcc repo for x86_64, aarch64 mingw targets has been detected. The patch to resolve the regression is on its way to the mailing list. - Validating public weekly builds on GitHub before making the repo public. Regards, Evgeny From: "Nathalie Chan King Choy (Windows on Arm)" <woa(a)hub.corecollective.dev> Date: Tuesday, 7 July 2026 at 16:53 To: Evgeny Karpov Cc: CoreCollective Windows on Arm Subject: Fwd: [CoreCollective WoA] Status of MinGW & GCC blockers for Strawberry Perl enablement? Perl enablement? Hi Evgeny, I received the Linaro WoA working group backlog and am working on updating it for use by the CoreCollective WoA working group. For Strawberry Perl, the last status was that it's blocked on MinGW and GCC. You were recommended as the person to ask about it: What are the blockers & what's the latest status on them? Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups

1 0

Fwd: [EXTERNAL] Re: Public tracker updates
by Nathalie Chan King Choy (Windows on Arm) 10 Aug '26

10 Aug '26

---------- Forwarded message --------- From: "Nathalie Chan King Choy (Windows on Arm)" <woa(a)hub.corecollective.dev> Date: Thursday, 25 June 2026 at 14:31:18 UTC-7 To: Anthony Roberts (Linaro) Cc: Omair Javaid (Linaro) , CoreCollective Windows on Arm No, they are not yet. Good, thanks for update, I was just checking we are aligned on this. ------------------------------ *From:* Anthony Roberts *Sent:* Thursday, June 25, 2026 3:11 AM *To:* Gleb Khmyznikov *Cc:* Omair Javaid ; CoreCollective Windows on Arm *Subject:* Re: [EXTERNAL] Re: [CoreCollective WoA] Public tracker updates Hi Gleb, I will attempt to drive sglang, I will try to speak to them next week - it's possible they may just not want to support Windows full stop (nginx was a case of this historically, they accepted PRs to build it, and allowed community builds, but wouldn't support it officially with builds). For temporalio, is cryptography shipping wheels now? As per Mayank's email, the work is already done, but it relies on cryptography to build. Therefore, I can't proceed until the upstream blocker is resolved. Thanks, Anthony On Wed, 24 Jun 2026 at 23:38, Gleb Khmyznikov wrote: follow up: NV works on cuda-python wheels and cuda-bindings. Current ETA is mid Aug. ------------------------------ *From:* Gleb Khmyznikov *Sent:* Tuesday, June 23, 2026 11:08 AM *To:* Anthony Roberts ; Omair Javaid *Cc:* CoreCollective Windows on Arm *Subject:* Re: [EXTERNAL] Re: [CoreCollective WoA] Public tracker updates Good day Anthony and everyone. - *sglang *is indeed even Linux only, no macos options. Which is might be a good win for us if we can make the support happen. @Anthony Roberts do you see how we can reach them in DM? Can you drive this? - *tree-sitter-languages, pyiceberg* marked your findings in our tracker. - *cuda-bindings* I still didn't get the response from NV. They may be in a on fire situation, I see the signals about the potential delay of CUDA SDK public availability. - *temporalio* @Omair Javaid do you guys aligned on this with @Anthony Roberts ? - *clickhouse-connect* is available on clickhouse-connect · PyPI <https://pypi.org/project/clickhouse-connect/#files> Great push @Omair Javaid - *zopfli* is available as well: zopfli · PyPI <https://pypi.org/project/zopfli/#files> @Anthony Roberts please let me know if I missed something regardless the previous list of work you had, any other blockers you have? Feel free to nudge me more frequent. ------------------------------ *From:* 'Gleb Khmyznikov' via CoreCollective Windows on Arm *Sent:* Monday, June 15, 2026 2:38 PM *To:* Anthony Roberts ; Omair Javaid *Cc:* CoreCollective Windows on Arm *Subject:* Re: [EXTERNAL] Re: [CoreCollective WoA] Public tracker updates Thanks for investigation, I’ve sent the email to NV about cuda-bindings. Get Outlook for iOS <https://aka.ms/o0ukef> ------------------------------ *From:* Anthony Roberts *Sent:* Monday, 15 June 2026 05:34:05 *To:* Omair Javaid *Cc:* Gleb Khmyznikov ; CoreCollective Windows on Arm *Subject:* [EXTERNAL] Re: [CoreCollective WoA] Public tracker updates Hi All, Regarding these: sglang: I suspect we'd need to reach out to the developers directly via the contact email address, to see why they have ignored the PR. I suspect they don't want the maintenance overhead of Windows, too. If x64 Windows is also missing, I suspect this could be a decent candidate to argue doesn't need porting. tree-sitter-languages: As per their repo, the library is unmaintained (https://github.com/ grantjenks/py-tree-sitter-languages#status) - they offer an alternative there, which already has ARM64 wheels: https://pypi.org/project/tree- sitter-language-pack pyiceberg: Blocked on pyarrow cuda-bindings: We'll need to wait for the public CUDA SDK for this one, unless we're happy to use pre-release versions and not commit anything until public ones are out - are NV already working on this themselves, is it worth checking? temporalio: Worth an investigation into the build failures Omair is seeing, and what is causing them. I'll try to look into this one, assuming Omair hasn't yet. clickhouse-connect: Looks like Omair's issue spurred them into doing it, no action is required from us zopfli: Same thing, they have also done the work for the wheel to be released Thanks, Anthony On Tue, 9 Jun 2026 at 13:55, Omair Javaid wrote: HI Gleb, Thanks for this update. I created issues for some of the missing packages. See the links inline below. On Sun, 7 Jun 2026 at 04:19, 'Gleb Khmyznikov' via CoreCollective Windows on Arm wrote: Happy weekend everyone. I've updated our public <https://github.com/khmyznikov/PyEnv-WoA-State/issues/1> tracker to align with Tony tracker <https://tonybaloney.github.io/windows-arm64-wheels/>. We are at 95% completion. Missing packages added: - *sglang *- https://github.com/sgl-project/sglang/pull/19706 windows only, someone from the community initiated the support, but looks abandoned. - *tree-sitter-languages* - development looks stale. - *pyiceberg* https://github.com/apache/iceberg-python/issues/3473 - *cuda-bindings* - *temporalio* https://github.com/temporalio/sdk-python/issues/1592 - *clickhouse-connect* https://github.com/ClickHouse/clickhouse-connect/issues/785 - *zopfli* https://github.com/fonttools/py-zopfli/issues/32 Anthony, you might be interested in that since nobody took it yet for enablement. Let me know if you start something from this list. P.S. I've added crypto monitoring action <https://github.com/CoreCollective-dev/windows-on-arm-wg/actions/workflows/m…> to our core collective repo.

1 0