-
Notifications
You must be signed in to change notification settings - Fork 15
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
JIT input files and code coverage #1736
Comments
Interesting...will do some testing and get back. |
Can give it a try as following:
|
That is looking like it has potential. Here's the build process that seems to work from a pristine state:
So that's a bit cumbersome, but it seems that, if the modified Makefile could be copied in instead (in place of the default Makefile) for sims that are compiled with coverage flags, then the necessity to run with expected failure, edit the default Makefile, remove the original .so, and re-make might be avoided. Is there a way to identify a build-with-coverage, and conditionally identify which Makefile to populate jitlib with? |
Yeah, the workaround takes some manual work. Current JIT input code doesn't generate .so target with trick or trick system CXXFLAGS like for .o target and it doesn't check if build-with-coverage. We'll look into this to make needed update such as to update trick code to have coverage flags for .so in jitlib Makefile if jit input is built with coverage. |
Noticed that a sim built with code-coverage flags
-fprofile-arcs -ftest-coverage
will not run a JIT-input file, it cannot load the generated .so file.Is there a workaround?
The text was updated successfully, but these errors were encountered: