Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

rust-lang / miri Public

Notifications You must be signed in to change notification settings
Fork 355
Star 4.8k

Code
Issues 139
Pull requests 13
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Detect mixed-size and mixed-atomicity non-synchronized accesses#3137

Merged

bors merged 8 commits intorust-lang:masterrust-lang/miri:masterfrom RalfJung:data-raceRalfJung/miri:data-raceCopy head branch name to clipboard

Oct 24, 2023

+416-225

Conversation Commits8 (8)Checks Files changed

Commits

Commits on Oct 23, 2023

data_race: clarify and slightly refactor non-atomic handling
RalfJung
committed
data_race: detect races between atomic and non-atomic accesses, even if both are reads
RalfJung
committed
detect mixed-size atomic accesses
RalfJung
committed
clean up imperfect overlap detection in weak-mem emulation
RalfJung
committed
don't talk about 'Data race' when both accesses are atomic
RalfJung
committed

Commits on Oct 24, 2023

fix error read-read reporting when there's also an unsynchronized non-atomic read (which is fine)
RalfJung
committed
futex text: avoid spurious non-atomic reads
RalfJung
committed
we don't support thread::scope on freebsd
RalfJung
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.