diff options
| author | bors <bors@rust-lang.org> | 2024-12-03 15:33:55 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-12-03 15:33:55 +0000 |
| commit | 490b2cc09860dd62a7595bb07364d71c12ce4e60 (patch) | |
| tree | 5d2dafd5435dd922f5f985755e7a8e0ab368619a /compiler/rustc_const_eval | |
| parent | 8575f8f91bbd7dca529d362afc8117db74661c3b (diff) | |
| parent | a69fe84ec841c20d229711d6861c5d889851e7f5 (diff) | |
| download | rust-490b2cc09860dd62a7595bb07364d71c12ce4e60.tar.gz rust-490b2cc09860dd62a7595bb07364d71c12ce4e60.zip | |
Auto merge of #133792 - lqd:jemallocup, r=Mark-Simulacrum
switch `jemalloc-sys` back to `tikv-jemalloc-sys`, and update to 0.6.0 Some context: - we used to use jemalloc bindings from https://github.com/gnzlbg/jemallocator, since #55238 - that crate was abandoned, picked up as a fork in https://github.com/tikv/jemallocator, so we switched to that in #83152. - then they were able to publish to the original `jemalloc-sys` bindings crate, and `jemalloc-sys` and `tikv-jemalloc-sys` became the same thing -- so I switched back to the OG crate in #96790 - they're now having publishing problems again: I've been waiting for https://github.com/tikv/jemallocator/pull/96 for the `jemalloc-sys` 0.6.0 update for a few months, but `tikv-jemalloc-sys` is already updated to 0.6.0. A perf run showed some improvements, so this PR switches back to `tikv-jemalloc-sys` to update to 0.6.0.
Diffstat (limited to 'compiler/rustc_const_eval')
0 files changed, 0 insertions, 0 deletions
