-
Notifications
You must be signed in to change notification settings - Fork 1
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
openmp-extractor is broken #118
Comments
Alternative, you can update the tutorial to work with llvm 10.x the source codes are imported into https://github.com/freeCompilerCamp/code-for-llvm-tutorials/tree/master/OpenMP-Extractor It works on my local machine, using latest llvm:
|
the execution has some error in freeCC's terminal
|
I built a fresh LLVM off github's 10.x today . It works
|
@ouankou It seems that the verison of llvm our terminal uses (May 4th) has some bug. Later version (june 17th) fixed it. Can you update llvm? |
@chunhualiao For now, in that tutorial I specified that it uses our initial docker image with LLVM 8.x on Ubuntu 16.04 (freeCompilerCamp/freecompilercamp.github.io@c662a75). I'll check your new code and update the tutorial to work with LLVM 10.x. The new docker images are being built, which will take a few hours. |
@chunhualiao I've pushed the latest LLVM 10.x build to FreeCC, which is the exactly same version of your local LLVM build. However, it still throws the same error in the FreeCC terminal. Would you mind sharing your compilation parameters for building LLVM? What I use is: ...
cmake -G Ninja -DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_INSTALL_PREFIX=$LLVM_PATH -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;compiler-rt;openmp" -DCLANG_BUILD_EXAMPLES=1 $LLVM_SRC/llvm
ninja install -j8 -l8 |
http://freecompilercamp.org/openmp-extractor/
It seems like the default container uses llvm 10.x while the tutorial was developed to work with the older llvm.
Can you prepare an old version llvm container to restore this tutorial?
You may want to check which old version of llvm we used before.
The text was updated successfully, but these errors were encountered: