We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was playing with zstd yesterday. The Makefile is easy to play with, just do:
# sudo service redis-server start # Remember to turn Redis on. CC=$SOUPER_BIN/sclang make -j
(Aside) The zstd runtime was worse worse with Souper. Is Souper is breaking cache boundaries or branch predictions?
I noticed Souper had a really hard time spreading load across cores when compiling a wllvm fat IR file.
# What I remember running, might have a typo LLVM_COMPILER=clang CC=wllvm make -j extract-bc pkg-config $SOUPER_BIN/sclang pkg-config.bc
Is there a flag I am missing to break Z3 solves into smaller chunks, or should I noodle on a PR?
Also, similer to gcc -fverbose-asm, how would you get the optimizations Souper produces printed as assembler comments?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I was playing with zstd yesterday. The Makefile is easy to play with, just do:
(Aside) The zstd runtime was worse worse with Souper. Is Souper is breaking cache boundaries or branch predictions?
I noticed Souper had a really hard time spreading load across cores when compiling a wllvm fat IR file.
Is there a flag I am missing to break Z3 solves into smaller chunks, or should I noodle on a PR?
Also, similer to gcc -fverbose-asm, how would you get the optimizations Souper produces printed as assembler comments?
The text was updated successfully, but these errors were encountered: