Currently if you run
seq 1 100000 >one
seq 1 4 100000 >two
git diff --no-index --histogram one two
you might run into memory issues. After applying the last patch of this series
you only have to wait a bit (as it doesn't fix run time complexity), but
computes the result with less memory pressure.
Thanks,
Stefan
Stefan Beller (3):
xdiff/xhistogram: pass arguments directly to fall_back_to_classic_diff
xdiff/xhistogram: factor out memory cleanup into free_index()
xdiff/xhistogram: move index allocation into find_lcs
xdiff/xhistogram.c | 117 +++++++++++++++++++++++++--------------------
1 file changed, 66 insertions(+), 51 deletions(-)
--
2.18.0.233.g985f88cf7e-goog
