Don't generate C code for extern functions that are never called - #1440
Merged
Alasdair merged 1 commit intoSep 9, 2025
Merged
Conversation
If you have a function that is `extern` with a fallback, like this:
```
val print_step = pure {c: "print_step"} : unit -> unit
function print_step() = ()
```
Then Sail will generate C code for the Sail version of the function, but then never call it. This hopefully avoids that.
Test Results 15 files 33 suites 0s ⏱️ Results for commit a2efc7c. |
Collaborator
|
Yes, seems better to avoid doing this. Especially with the |
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.
If you have a function that is
externwith a fallback, like this:Then Sail will generate C code for the Sail version of the function, but then never call it. This hopefully avoids that.