Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump jemalloc 0.6.0 #96

Open
wants to merge 14 commits into
base: master
Choose a base branch
from
Open

Bump jemalloc 0.6.0 #96

wants to merge 14 commits into from

Conversation

BusyJay
Copy link
Member

@BusyJay BusyJay commented Jul 14, 2024

No description provided.

tusharmath and others added 14 commits October 8, 2023 10:13
Signed-off-by: Tushar Mathur <tusharmath@gmail.com>
Signed-off-by: Jack Kleeman <jackkleeman@gmail.com>
The configure step for jemalloc fails to recognize the rustc
target `riscv64gc-unknown-linux-musl`:
```
  --- stderr
  Invalid configuration `riscv64gc-unknown-linux-musl': machine `riscv64gc-unknown' not recognized
  configure: error: /bin/sh build-aux/config.sub riscv64gc-unknown-linux-musl failed
  thread 'main' panicked at /home/marv/.cargo/registry/src/index.crates.io-6f17d22bba15001f/jemalloc-sys-0.5.4+5.3.0-patched/build.rs:351:9:
  command did not execute successfully: cd "/mnt/data/devel/ripgrep/target/release/build/jemalloc-sys-eb3f9d51d93e319f/out/build" && CC="cc" CFLAGS="-O3 -ffunction-sections -fdata-sections -fPIC -gdwarf-4 -fno-omit-frame-pointer -march=rv64gc -mabi=lp64d -mcmodel=medany -Wall -g -ggdb3 -O0" CPPFLAGS="-O3 -ffunction-sections -fdata-sections -fPIC -gdwarf-4 -fno-omit-frame-pointer -march=rv64gc -mabi=lp64d -mcmodel=medany -Wall -g -ggdb3 -O0" LDFLAGS="-O3 -ffunction-sections -fdata-sections -fPIC -gdwarf-4 -fno-omit-frame-pointer -march=rv64gc -mabi=lp64d -mcmodel=medany -Wall -g -ggdb3 -O0" "sh" "/mnt/data/devel/ripgrep/target/release/build/jemalloc-sys-eb3f9d51d93e319f/out/build/configure" "--disable-cxx" "--enable-doc=no" "--enable-shared=no" "--with-jemalloc-prefix=_rjem_" "--with-private-namespace=_rjem_" "--host=riscv64gc-unknown-linux-musl" "--build=riscv64gc-unknown-linux-musl" "--prefix=/mnt/data/devel/ripgrep/target/release/build/jemalloc-sys-eb3f9d51d93e319f/out"
  expected success, got: exit status: 1
```

Add an entry to build.rs to translate between the GNU target and rustc
target in order to work around the mismatch

Signed-off-by: Marvin Schmidt <marv@exherbo.org>
Signed-off-by: Val Packett <val@packett.cool>
As otherwise the commit doesn't reliably download on new checkout

Signed-off-by: Jack Kleeman <jackkleeman@gmail.com>
* Use --with-version when configuring jemalloc

This also changes the metadata of the version so that jemalloc still
reports the same version as before.

Fixes #76

Signed-off-by: Rafael Ávila de Espíndola <rafael@espindo.la>
- add m1 macos ci target
- feat: add profiling options

Signed-off-by: Dan Cline <6798349+Rjected@users.noreply.github.com>
)

Close #81.

Signed-off-by: fys <fengys1996@gmail.com>
jemalloc defaults to enabling stats if `--enable-stats` is not
present and `--disable-stats` was not set: https://github.com/jemalloc/jemalloc/blob/fa451de17fff73cc03c31ec8cd817d62927d1ff9/configure.ac#L1331-L1333

the stats feature was always enabled by default and never
respected if someone were to remove the stats feature as
no logic was added for setting `--disable-stats`. to avoid
breaking other user's setups who are relying on this behaviour,
set stats as a default feature.

Signed-off-by: strawberry <strawberry@puppygock.gay>
macos-latest has been switched from x86_64 to aarch64
(https://github.com/actions/runner-images/blob/main/README.md)

Signed-off-by: YEUNG King On <koyeung@gmail.com>
Signed-off-by: Jay Lee <busyjaylee@gmail.com>
Signed-off-by: Torrekie <31795847+Torrekie@users.noreply.github.com>
Signed-off-by: Jay Lee <BusyJay@users.noreply.github.com>
Signed-off-by: Jay Lee <busyjaylee@gmail.com>
@miried
Copy link

miried commented Oct 16, 2024

Can this be merged?

@BusyJay
Copy link
Member Author

BusyJay commented Oct 16, 2024

Unfortunately no. DCO check failed due to dcoapp/app#114. And I don't have the permission to force merge it yet.

/cc @siddontang

@ti-chi-bot ti-chi-bot bot requested a review from siddontang October 16, 2024 08:29
@miried
Copy link

miried commented Oct 21, 2024

I'm afraid it will be difficult to get those commit messages fixed after such a long time.

Can @siddontang unblock this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.