[NVPTX] fix illegal name for .extern .shared global varaibles #173018
+13
−2
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.
In ptx we can create a GV in AS(3) that will be compiled to a
.extern .sharedin ptx. Since the.extern .sharedis not an "extern" in the traditional sense of the word it will not be linked based on name but rather refer to the shared memory allocated at kernel launch.Since we don't care about the name it's tempting to make the GV unnamed. Then the problem that the
nameUnamedGlobalswill use a name for the global that is invalid ptx occurs. For non-extern globals, this is later fixed by running theNVPTXAssignValidGlobalNamespass. However, It makes sure to not touch externs as changing the name of "traditional externs" will cause linking issues down the road.This MR treats
.extern .sharedin the same manner as non-extern globals duringNVPTXAssignValidGlobalNamesto fix the invalid names given bynameUnamedGlobals.