-
Notifications
You must be signed in to change notification settings - Fork 32
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
Compiling a Cilk/C++ program with Cilkscale instrumentation prints LLVM IR to stderr #129
Labels
bug
Something isn't working
Comments
neboat
added a commit
to neboat/opencilk-project
that referenced
this issue
Aug 25, 2022
…ug statement to fix issue OpenCilk#129.
Merged
This issue is resolved in OpenCilk v2.0.1. |
neboat
added a commit
to neboat/opencilk-project
that referenced
this issue
Nov 28, 2023
…ug statement to fix issue OpenCilk#129.
kennyzzhang
pushed a commit
to kennyzzhang/opencilk-project
that referenced
this issue
Feb 2, 2024
…ug statement to fix issue OpenCilk#129.
neboat
added a commit
to neboat/opencilk-project
that referenced
this issue
Jan 15, 2025
…ug statement to fix issue OpenCilk#129.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When I compile a Cilk/C++ program with Cilkscale instrumentation (
-fcilktool=cilkscale
), LLVM IR for my Cilk function is printed tostderr
. Compilation seems to proceed OK otherwise: the binary runs and passes correctness tests, and Cilkscale outputs its work-span analysis report as expected.The same is true when compiling with Cilkscale-benchmark instrumentation (
-fcilktool=cilkscale-benchmark
).I do not see this behavior with Cilk/C code or if I use OpenCilk 1.0.
Expected behavior
No printing of LLVM IR when compiling a Cilk/C++ program with Cilkscale instrumentation.
OpenCilk version
opencilk/v2.0
for all repos)System information
Steps to reproduce (include relevant output)
Minimal working example,
hello.cpp
:Compile with Cilkscale instrumentation:
Run:
The text was updated successfully, but these errors were encountered: