| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2024-10-06 | Auto merge of #3936 - YohDeadfall:rust-analyzer-conf, r=RalfJung | bors | -39/+87 | |
| Added rust-analyzer instructions for Helix That pull request adds information on how to configure Helix to use `rust-analyzer`, and moves the existing configuration to the `src/etc` directory as it's in the `rust` repository. Not adding instructions for other IDE because there's a link leading to the how-to for `rustc`. | ||||
| 2024-10-06 | tweak the hint | Ralf Jung | -8/+3 | |
| 2024-10-05 | Fix up tests | Michael Goulet | -2/+49 | |
| 2024-10-05 | Stabilize `std::io::ErrorKind::QuotaExceeded` | Pavel Grigorenko | -1/+1 | |
| Also drop "Filesystem" from its name | ||||
| 2024-10-05 | Added rust-analyzer instructions for Helix | Yoh Deadfall | -38/+91 | |
| 2024-10-05 | avoid pthread_attr_t in tests | Ralf Jung | -18/+24 | |
| 2024-10-05 | Auto merge of #3940 - rust-lang:refutable_slice, r=RalfJung | bors | -33/+34 | |
| Prefer refutable slice patterns over len check + index op Just something I noticed while reviewing other PRs We do it for shim arguments almost everywhere, but when the size is not statically known, we didn't use the helpers as they rely on array ops. But we can avoid a len check followed by several index ops by just using a refutable slice pattern with `let else`. The pattern is so common, it seems almost worth a dedicated macro | ||||
| 2024-10-05 | Auto merge of #3943 - RalfJung:pthread-mutex-reentrant, r=RalfJung | bors | -15/+51 | |
| pthread mutex: better error in reentrant-locking-UB Also test reentrant locking of PTHREAD_MUTEX_INITIALIZER | ||||
| 2024-10-05 | pthread mutex: better error in reentrant-locking-UB, also test ↵ | Ralf Jung | -15/+51 | |
| PTHREAD_MUTEX_INITIALIZER | ||||
| 2024-10-04 | Prefer refutable slice patterns over len check + index op | Oli Scherer | -33/+34 | |
| 2024-10-04 | Implement LLVM x86 gfni intrinsics | Tobias Decking | -0/+722 | |
| 2024-10-04 | clippy | Ralf Jung | -2/+1 | |
| 2024-10-04 | Merge from rustc | The Miri Cronjob Bot | -7/+7 | |
| 2024-10-04 | Preparing for merge from rustc | The Miri Cronjob Bot | -1/+1 | |
| 2024-10-03 | make sure we also detect mixed-size races that begin at different addresses | Ralf Jung | -1/+47 | |
| 2024-10-03 | fmt | Ralf Jung | -19/+27 | |
| 2024-10-03 | Merge from rustc | Ralf Jung | -990/+988 | |
| 2024-10-03 | Preparing for merge from rustc | Ralf Jung | -1/+1 | |
| 2024-10-03 | Auto merge of #127912 - joboet:tls_dtor_thread_current, r=cuviper | bors | -7/+7 | |
| std: make `thread::current` available in all `thread_local!` destructors ... and thereby allow the panic runtime to always print the right thread name. This works by modifying the TLS destructor system to schedule a runtime cleanup function after all other TLS destructors registered by `std` have run. Unfortunately, this doesn't affect foreign TLS destructors, `thread::current` will still panic there. Additionally, the thread ID returned by `current_id` will now always be available, even inside the global allocator, and will not change during the lifetime of one thread (this was previously the case with key-based TLS). The mechanisms I added for this (`local_pointer` and `thread_cleanup`) will also allow finally fixing #111272 by moving the signal stack to a similar runtime-cleanup TLS variable. | ||||
| 2024-10-02 | epoll: remove extraneous clone of ready_list | Frank Rehwinkel | -2/+1 | |
| A simplification that doesn't impact the epoll implementation's logic. It is not necessary to clone the ready_list before reading its `is_empty` state. This avoids the clone step but more importantly avoids the invisible drop step of the clone. | ||||
| 2024-10-02 | epoll: add vector clock to the epoll ready_list | Frank Rehwinkel | -119/+67 | |
| This adds a VClock to the epoll implementation's ready_list and has this VClock synced from the thread that updates an event in the ready_list and then has the VClocks of any threads being made runnable again, out of the calls to epoll_wait, synced from it. | ||||
| 2024-10-02 | epoll: remove unnecessary instructions | Frank Rehwinkel | -3/+0 | |
| A couple of instructions were left over from an earlier rebase it would seem. They don't impact the logic but the ready_list type is about to change in the next commit. Rather than modify one of these lines in the commit that changes ready_list, only to have these lines removed later on, remove them now. They don't impact the tests results. | ||||
| 2024-10-02 | epoll: add data_race test | Frank Rehwinkel | -0/+108 | |
| This test demonstrates the need to synchronize the clock of the thread waking up from an epoll_wait from the thread that issued the epoll awake event. | ||||
| 2024-10-02 | bless miri tests | joboet | -7/+7 | |
| 2024-10-01 | make InterpResult a dedicated type to avoid accidentally discarding the error | Ralf Jung | -728/+734 | |
| 2024-10-01 | add set_last_error_and_return_i32 helper and use it in a few places | Ralf Jung | -27/+28 | |
| 2024-10-01 | make set_last_error directly callable on a bunch of ways to represent errors | Ralf Jung | -80/+88 | |
| 2024-10-01 | move io error handling helpers to their own file | Ralf Jung | -184/+193 | |
| 2024-10-01 | Refactor return_read_bytes_and_count and return_written_byte_count_or_error | tiif | -67/+76 | |
| 2024-09-30 | panic when an interpreter error gets unintentionally discarded | Ralf Jung | -3/+8 | |
| 2024-09-30 | Auto merge of #131036 - RalfJung:miri-sync, r=RalfJung | bors | -474/+602 | |
| Miri subtree update r? `@ghost` | ||||
| 2024-09-29 | let rustfmt format imports | Ralf Jung | -319/+255 | |
| 2024-09-29 | bump few deps | klensy | -63/+24 | |
| 2024-09-29 | skip old getrandom crate on Solaris | Ralf Jung | -5/+10 | |
| 2024-09-28 | Auto merge of #3918 - devnexen:solaris_arc4random_buf, r=RalfJung | bors | -4/+31 | |
| implements arc4random_buf shim for freebsd/solarish platforms. close #3914 | ||||
| 2024-09-28 | make sure the new function is tested | Ralf Jung | -4/+4 | |
| 2024-09-28 | implements arc4random_buf shim for freebsd/solarish platforms. | David Carlier | -0/+27 | |
| close #3914 | ||||
| 2024-09-28 | add tests for validity of Box with custom allocator | Ralf Jung | -0/+99 | |
| 2024-09-28 | Further clarificarion for atomic and UnsafeCell docs: | Ralf Jung | -0/+17 | |
| - UnsafeCell: mention the term "data race", and reference the data race definition - atomic: failing RMWs are just reads, reorder and reword docs | ||||
| 2024-09-28 | allow mixed-size atomic reads | Ralf Jung | -153/+202 | |
| 2024-09-28 | miri: no longer complain about read-read races | Ralf Jung | -122/+43 | |
| 2024-09-27 | Update cc to 1.1.22 | Chris Denton | -6/+33 | |
| 2024-09-26 | Auto merge of #3916 - rust-lang:rustup-2024-09-26, r=RalfJung | bors | -21/+21 | |
| Automatic Rustup | ||||
| 2024-09-26 | remove some clippy lints from the list that we do not even trigger any more | Ralf Jung | -2/+0 | |
| 2024-09-26 | fix clippy::needless_return | Ralf Jung | -13/+13 | |
| 2024-09-26 | clippy | Ralf Jung | -5/+7 | |
| 2024-09-26 | bump rustc-build-sysroot version | Ralf Jung | -3/+3 | |
| 2024-09-26 | Preparing for merge from rustc | The Miri Cronjob Bot | -1/+1 | |
| 2024-09-25 | Auto merge of #3915 - RalfJung:target-json-test, r=RalfJung | bors | -27/+25 | |
| switch custom target JSON test to a less exotic target We used to test an AVR target here, but while it is nice to test a 16bit target, it is also currently the case that rustc CI does not even check that libcore builds on a 16bit target -- and we don't want Miri to be in the game of maintaining that support. (See https://github.com/rust-lang/rust/issues/130818.) So let's use a tier 2 target as the basis for testing a custom JSON target. (FWIW, we also test wasm32-wasip2 which is tier 3, but I expect it will become tier 2 Soon-ish.) | ||||
| 2024-09-25 | switch custom target JSON test to a less exotic target | Ralf Jung | -27/+25 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |