-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[HLSL] Appropriately set function attribute optnone #125937
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
63a728d
[HLSL] Set function optnone attribute appropriately
bharadwajy 00897b8
[HLSL] Delete the change that sets non-entry functions of a library
bharadwajy 54b1e87
Add comment
bharadwajy 37bcc29
Delete braces around simple single-statement body of if statement
bharadwajy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that these already have "noinline", I'm surprised that the logic in "SetLLVMFunctionAttributesForDefinition" doesn't already put optnone on these functions. Is something undoing this later?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The entry function that is created and whose attribute is set to
noinline
in this function is different from thatSetLLVMFunctionAttributesForDefinition()
looks at.GenerateCode(GlobalFnDecl, MangledFn, ...)
callsStartFunction(GlobalFnDecl, ResTy, MangledFn, ...)
which in turn callsemitEntryFunction(FnDecl, MangledFn)
.emitEntryFunction(FnDecl, MangledFn, ...)
constructs a new entry functionEntryFn
, sets linkage ofMangledFn
to beinternal
to arrange it to be inlined inEntryFn
etc., and callssetHLSLEntryAttributes(FnDecl, EntryFn)
to set attributes ofEntryFn
.SetLLVMFunctionAttributesForDefinition(...)
sets attributes ofMangledFn
. So the logic in that function checks attributes forMangledFn
and not for the createdEntryFn
.Hence setting
optnone
attribute insetHLSLEntryAttributes(FnDecl, EntryFn)
ofEntryFn
at the time of its set up seemed appropriate - if optimizations are disabled.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. I think a comment to the effect of "We need to manually set attributes here instead of relying on
SetLLVMFunctionAttributesForDefinition
to pick them up since these functions are injected by the compiler and won't go through the normal flow" (please reword as necessary to be accurate...) would be a good idea here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment added. Thanks!