Support object files in JIT#290
Open
rayegun wants to merge 3 commits intoDrTimothyAldenDavis:dev3from
Open
Conversation
Contributor
Author
|
Hmmmm. This commit history does not look right haha. Let me try to fix that |
Contributor
Author
|
Oh it's because I made it against stable oops. That's much better |
Owner
|
The Source/fy files are now in the Source/jitifyer folder. Source/GrB_Global_set.c has been moved to Source/get_set/GrB_Global_set.c. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I consider this WIP because I have some more testing to do on other platforms. This PR adds a few new global options, as well as the ability to treat a string as a path for the JIT. Sorry it took so long I was debugging going from macOS to linux.
The object file vs header file and LTO are handled by the user-defined compiler flags, not by any hardcoded controls. This is fairly natural, as the LTO handling may differ slightly between different linkers and compiler drivers.
In a separate PR I will add the support to control JIT compilation on an operator level.