- User Since
- Jan 28 2016, 4:53 PM (372 w, 3 d)
Nov 11 2019
Remove the benchmark
@terrelln No one has responded to http://lists.llvm.org/pipermail/llvm-dev/2019-October/136337.html yet. I think we can just commit the code change for now. Do you need help for committing the patch?
Oct 28 2019
Use triple x86_64 in tests.
Oct 25 2019
@smeenai yeah I will
Oct 24 2019
Merged into D69294
- Merge D69293 into this diff.
- Fix all comments.
Can you try posix_fallocate(fd, 0, len) and see how it performs under memory pressure with btrfs+compression?
Oct 23 2019
I also agree with this. I think llvm/benchmarks would be fine for now either way, but with more benchmarks (which hopefully would be there at some point, I had plans of adding some for a while now but I'm not sure when I'll get to that) subdirectories make sense.
Oct 22 2019
I'll update the description to answer questions, and make the requested changes. I've also answered questions inline below.
Maybe this should be merged with https://reviews.llvm.org/D69294. Since we are moving to a single repository that contains both llvm and lld, we no longer have to split a commit at svn repo boundaries. Since this flag will be used only by lld at least for a while, it feels more natural to commit this and the other one as a single commit.
If you really want to make this fast, I think Intel processors have special-purpose instructions to accelerate SHA1 computation. Have you consider using them?