Remove .Cold calling convention. #6596
Merged
+12
−26
Conversation
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
This isn't a stable, defined calling convention, so it shouldn't be grouped in with the others. Closes ziglang#6556
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.
This isn't a stable, defined calling convention, so it shouldn't be
grouped in with the others.
Closes #6556
I said "keep it as an implementation detail" in the original issue, but it seems like ZigLLVMAddFunctionAttrCold doesn't change the calling convention.
I think using the cold calling convention for .Unspecified calling convention functions which are
@setCold(true)can be a different PR.