You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CpuMath Enhancement: Make bound checking of loops in hardware intrinsics more efficient #835
changed the title [-]Make bound checking of loops in hardware intrinsics more efficient[/-][+]CpuMath Enhancement: Make bound checking of loops in hardware intrinsics more efficient[/+]on Sep 6, 2018
This issue has been automatically marked no-recent-activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no-recent-activity.
This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.
Activity
[-]Make bound checking of loops in hardware intrinsics more efficient[/-][+]CpuMath Enhancement: Make bound checking of loops in hardware intrinsics more efficient[/+]danmoseley commentedon Sep 6, 2018
As well as doing this, we should make sure there's a code gen issue open.
rosebyte commentedon Sep 3, 2026
Could you provide evidence how much performance we get by the optimisation?
dotnet-policy-service commentedon Sep 3, 2026
This issue has been marked
needs-author-actionand may be missing some important information.dotnet-policy-service commentedon Oct 5, 2026
This issue has been automatically marked
no-recent-activitybecause it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will removeno-recent-activity.dotnet-policy-service commentedon Oct 19, 2026
This issue will now be closed since it had been marked
no-recent-activitybut received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.