RepoJournal
.NET

@dotnet

The .NET runtime, ASP.NET, and the C# tooling

Pick a date

  1. Wed 20 may
  2. Thu 21 may
  3. Sat 23 may
  4. Sun 24 may
  5. Mon 25 may
  6. Tue 26 may
  7. Wed 27 may
  8. Thu 28 may
  9. Fri 29 may
  10. Sat 30 may
  11. Sun 31 may
  12. Mon 1 jun
  13. Mon 8 jun
  14. Tue 9 jun
  15. Wed 10 jun
  16. Thu 11 jun
  17. Fri 12 jun
  18. Sat 13 jun
  19. Sun 14 jun
  20. Mon 15 jun
  21. Tue 16 jun
  22. Wed 17 jun
  23. Thu 18 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

The Wire · Showcase

JIT FLAGS BUG FIXES CRITICAL PATH FOR X86 ROTATE OPERATIONS

By RepoJournal · Filed · About .NET

The runtime shipped a precision fix that stops the JIT from incorrectly claiming rotate instructions set the zero flag, a bug that could silently corrupt conditional logic downstream.

The core issue landed in dotnet/runtime: ROL and ROR instructions on x86 only affect the carry flag (CF), not zero flag (ZF), but the JIT was claiming otherwise [1]. This matters because downstream code relies on those flag states to make branching decisions. If the JIT lies about which flags are set, you get silent logic corruption that's nearly impossible to debug in production. In parallel, the diagnostics team consolidated follow-ups to the cDAC refactor, cleaning up StackWalk documentation and fixing the DataGenerator build [2]. On the WASM front, the team split out browser compatibility work ahead of the Emscripten 5.0.6 bump, bumping Firefox support from 125.0.1 to 140.11.0esr and prepping the toolchain transition [3]. Roslyn fixed a records codegen bug where synthesized methods were making non-virtual calls to abstract methods, which violated the inheritance contract [4].

Action items

References

  1. [1] JIT: don't claim rotates set ZF on xarch ↗ dotnet/runtime
  2. [2] [cdac] Pipeline refactor + StackWalk doc cleanup + DataGenerator build fix ↗ dotnet/runtime
  3. [3] [browser][wasm] Prep changes ahead of emsdk bump ↗ dotnet/runtime
  4. [4] Records: Avoid synthesized non-virtual calls to abstract methods ↗ dotnet/roslyn

FAQ

What changed in .NET on June 15, 2026?
The runtime shipped a precision fix that stops the JIT from incorrectly claiming rotate instructions set the zero flag, a bug that could silently corrupt conditional logic downstream.
What should .NET teams do about it?
Review JIT flag fix [ref:1] before next runtime build - verify your rotate-dependent code paths • Track the Emscripten 5.0.6 bump; these WASM prep changes [ref:4] can ship independently • Test records with abstract method inheritance if you use C# 9+ record types
Which .NET repositories shipped on June 15, 2026?
dotnet/runtime, dotnet/roslyn

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.