Merged
Conversation
…123516) This pull request updates the following dependencies [marker]: <> (Begin:d3a5b203-1393-4534-5b62-08d8d8feb47e) ## From https://dev.azure.com/dnceng/internal/_git/dotnet-optimization - **Subscription**: [d3a5b203-1393-4534-5b62-08d8d8feb47e](https://maestro.dot.net/subscriptions?search=d3a5b203-1393-4534-5b62-08d8d8feb47e) - **Build**: [20260122.1](https://dev.azure.com/dnceng/internal/_build/results?buildId=2885421) ([298510](https://maestro.dot.net/channel/5172/azdo:dnceng:internal:dotnet-optimization/build/298510)) - **Date Produced**: January 22, 2026 10:56:49 PM UTC - **Commit**: [86dcbdbc1b8ee179c87278e3ccbccedd2ad49a2a](https://dev.azure.com/dnceng/internal/_git/dotnet-optimization?_a=history&version=GC86dcbdbc1b8ee179c87278e3ccbccedd2ad49a2a) - **Branch**: [refs/heads/main](https://dev.azure.com/dnceng/internal/_git/dotnet-optimization?version=GBrefs/heads/main) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [1.0.0-prerelease.25502.1 to 1.0.0-prerelease.26072.1][1] - optimization.linux-arm64.MIBC.Runtime - optimization.linux-x64.MIBC.Runtime - optimization.windows_nt-arm64.MIBC.Runtime - optimization.windows_nt-x64.MIBC.Runtime - optimization.windows_nt-x86.MIBC.Runtime - optimization.PGO.CoreCLR [1]: https://dev.azure.com/dnceng/internal/_git/dotnet-optimization/branches?baseVersion=GC71ce9774e9875270b80faaac1d6b60568a80e1fa&targetVersion=GC86dcbdbc1b8ee179c87278e3ccbccedd2ad49a2a&_a=files [DependencyUpdate]: <> (End) [marker]: <> (End:d3a5b203-1393-4534-5b62-08d8d8feb47e) Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: Drew Scoggins <anscoggi@microsoft.com>
Today, assertions for relops are represented as `relopVN OAK_[NOT]_EQUAL 0` - this forces most assertion consumers to call GetVNFunc over the relopVN to see if one of the operands matches thiers. This PR attempts to remove them and introduce `OAK_<relop>` so all assertions become just e.g. `op1VN OAK_LE op2VN`. The plan is to remove these: ``` (removed in this PR) O1K_CONSTANT_LOOP_BND (removed in this PR) O1K_CONSTANT_LOOP_BND_UN (removed in this PR) O1K_ARR_BND (will be removed in a follow up) O1K_BOUND_LOOP_BND, // X < CHECKED_BND (will be removed in a follow up) O1K_BOUND_OPER_BND, // X < CHECKED_BND + Y (removed in this PR) OAK_NO_THROW ``` Also, no longer weird `OAK_NO_THROW` without `op2`. It's now represented as a normal `op1VN (idx) OAK_LT_UN op2VN (len)` I need this simplification for some of the optimizations I have in mind (and enable many existing ops for 64-bit integers and floating points). Also, it makes it easier to implement a VN-mapped hash set to quickly validate that we definitely don't have assertions for the given VN. [Diffs](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1281385&view=ms.vss-build-web.run-extensions-tab) - slight improvements in size and TP. I tried to keep the size diffs minimal for the refactoring PR, but it was not possible without ugly hacks to make them exactly zero.
Addressed test hole discovered in #123832.
## Description The dogfooding documentation contained mixed .NET 9 and .NET 11 content. Since main branch now targets .NET 11 (pre-GA), the document has been updated to reference .NET 11 exclusively. ## Changes - **Package feeds**: `dotnet9` → `dotnet11` across all NuGet and Azure DevOps feed URLs - **Version numbers**: Updated SDK (`11.0.100-alpha.1.24556.7`), runtime (`11.0.0-alpha.1.24556.3`), and package version examples - **Download links**: Changed from `/9.0/daily/` to `/11.0/daily/` - **Error messages**: Updated NETSDK1045 error text to reference .NET 11.0 - **Runtime identifier**: Modernized from `win10-x64` to `win-x64` All examples, commands, and documentation now consistently reference .NET 11.0 target framework and alpha versioning scheme. <!-- START COPILOT CODING AGENT SUFFIX --> <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > Can you update this document to be exclusively about .NET 11. It has both .NET 9 and .NET 11 content in it. The main branch is now .NET 11 (not yet GA). </details> <!-- START COPILOT CODING AGENT TIPS --> --- ✨ Let Copilot coding agent [set things up for you](https://github.com/dotnet/runtime/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: richlander <2608468+richlander@users.noreply.github.com>
Copilot-authored pull requests run workflows with permissions lower than other PRs (including those submitted by external contributors). This blocks the issue-labeler workflow from being able to run on those PRs, leaving a prompt for the workflow to be approved. To run issue-labeler over these PRs as well as other PRs that have missed labeling (such as GitHub service interruptions when the events don't trigger), the PR label prediction workflow adds a cron schedule for as frequently as GitHub will run it (by using every 5 minutes). When triggered from the polling event, we collect the list of open and unlabeled PRs that have been updated since the last polling run (plus 5 extra minutes), and we run the issue-labeler prediction against those. This also updates the workflow_dispatch event to allow an empty list of PR numbers to force a polling event run. Addresses [(dotnet/issue-labeler#105) Pull Request Labeling does not run automatically for Copilot PRs](dotnet/issue-labeler#105) for this repository. If this approach proves to work well for this repository, we will replicate the fix to other repos. --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )