-
Notifications
You must be signed in to change notification settings - Fork 13.3k
notify Miri when intrinsics are changed #130228
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
rustbot has assigned @Mark-Simulacrum. Use |
|
I would rather that the team be notified. |
I don't know what the procedure is for landing this. Oli is on leave, so r=me if you want to land this now. |
@bors r=saethlin rollup |
…kingjubilee Rollup of 10 pull requests Successful merges: - rust-lang#129103 (Don't warn empty branches unreachable for now) - rust-lang#129696 (update stdarch) - rust-lang#129835 (enable const-float-classify test, and test_next_up/down on 32bit x86) - rust-lang#130077 (Fix linking error when compiling for 32-bit watchOS) - rust-lang#130114 (Remove needless returns detected by clippy in the compiler) - rust-lang#130168 (maint: update docs for change_time ext and doc links) - rust-lang#130228 (notify Miri when intrinsics are changed) - rust-lang#130239 (miri: fix overflow detection for unsigned pointer offset) - rust-lang#130244 (Use the same span for attributes and Try expansion of ?) - rust-lang#130248 (Limit `libc::link` usage to `nto70` target only, not NTO OS) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#130228 - RalfJung:intrinsics-notify, r=saethlin notify Miri when intrinsics are changed `@rust-lang/miri` should we notify the entire team, or should I just add myself?
@rust-lang/miri should we notify the entire team, or should I just add myself?