Skip to content

enable jemalloc debugging in unoptimized builds #17083

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

Merged
merged 1 commit into from
Sep 9, 2014
Merged

enable jemalloc debugging in unoptimized builds #17083

merged 1 commit into from
Sep 9, 2014

Conversation

thestinger
Copy link
Contributor

The performance hit from these checks is significant, but unoptimized
builds are already incredibly slow. Enabling these checks results in
better test coverage since there are bots doing unoptimized builds, and
the cost is relatively small in the context of an unoptimized build.
This also allows using JEMALLOC_FLAGS to override the default
configure flags.

The performance hit from these checks is significant, but unoptimized
builds are already incredibly slow. Enabling these checks results in
better test coverage since there are bots doing unoptimized builds, and
the cost is relatively small in the context of an unoptimized build.
This also allows using `JEMALLOC_FLAGS` to override the default
configure flags.
@alexcrichton
Copy link
Member

I suspect that if this turns out to slow down the bots unbearably, we can always revert it. Otherwise, the more debugging the merrier!

@thestinger
Copy link
Contributor Author

@alexcrichton: I think it just slows down allocation by 20-30%, and since the compiler only spends ~10% of the time in the allocator it shouldn't be that bad. It's really nice because it will mean sized deallocation errors get caught by the no optimization bots, along with lots of other checks like making sure all pointers passed to the API are within the bounds of a valid chunk + junk filling of all deallocated memory.

@alexcrichton
Copy link
Member

Sounds good to me!

bors added a commit that referenced this pull request Sep 9, 2014
The performance hit from these checks is significant, but unoptimized
builds are already incredibly slow. Enabling these checks results in
better test coverage since there are bots doing unoptimized builds, and
the cost is relatively small in the context of an unoptimized build.
This also allows using `JEMALLOC_FLAGS` to override the default
configure flags.
@bors bors closed this Sep 9, 2014
@bors bors merged commit 1ee099d into rust-lang:master Sep 9, 2014
@thestinger thestinger deleted the jemalloc branch September 10, 2014 06:55
lnicola pushed a commit to lnicola/rust that referenced this pull request Apr 20, 2024
ide: improve ReferenceCategoryType

It is bitset semantically --- many categorical things can be true about a reference at the same time.

In parciular, a reference can be a "test" and a "write" at the same time.
lnicola pushed a commit to lnicola/rust that referenced this pull request Apr 20, 2024
ide: improve ReferenceCategoryType

It is bitset semantically --- many categorical things can be true about a reference at the same time.

In parciular, a reference can be a "test" and a "write" at the same time.
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.

3 participants