Skip to content

Commit fccf45e

Browse files
folkertdevmike
authored andcommitted
fix gix-blame performance regresion
The issue was introduced in GitoxideLabs#1963, and incorrectly assumed that the `max-performance-safe` feature flag was only used to enable other feature flags. But this feature flag is itself used in various places, so failing to enable it leads to worse codegen. This issue was discussed/found in GitoxideLabs#2148
1 parent fa1026e commit fccf45e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

gix/Cargo.toml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -246,8 +246,8 @@ pack-cache-lru-static = ["gix-pack/pack-cache-lru-static"]
246246
## Provide a hash-map based LRU cache whose eviction is based a memory cap calculated from object data.
247247
pack-cache-lru-dynamic = ["gix-pack/pack-cache-lru-dynamic"]
248248

249-
## Enable all features required for performance. Currently, this is equivalent to `max-control`, as gix always uses zlib-rs.
250-
max-performance = ["max-control"]
249+
## Enable all features required for performance.
250+
max-performance = ["max-performance-safe"]
251251

252252
## Deprecated: gix always uses zlib-rs.
253253
zlib-ng = ["gix-features/zlib"]

0 commit comments

Comments
 (0)