Add INSTALLING and README Markdown format #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gonidelis
commented
Feb 23, 2021
| You can run the compiler out of its build tree, adding `/bin/clang` to | ||
| the build directory name. For example: | ||
|
|
||
| `./build/bin/clang fib.c -o fib -O3 -fopencilk` |
|
I like this suggestion. In fact, on the current development version of this repository, on the |
|
@neboat Thanks. Ok I hadn't noticed. My focus was on the example use case. Do as you please :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Although the installation instructions needed for openCilk are pretty straightforward, inexperienced users might find it difficult to guide themselves amd fully build openCilk from source with the given instructions. I started the PR with the initial idea of just adding this example use case line, but then I decided to do some extra housekeeping for the sake of "user-friendliness".
Even if the PR gets rejected, I would recommend just putting together the building commands in a serial order, along with the trivial
fib.ccompilation example.