This is an archive of the discontinued LLVM Phabricator instance.

[GlobalOpt][FIX] Do not embed initializers into AS!=0 globals
ClosedPublic

Authored by jdoerfert on Sep 6 2021, 2:05 PM.

Details

Summary

Not all address spaces support initializers for globals and we can
therefore not set them without checking if they are allowed. This
patch adds a hook into TTI to check if an AS allows non-undef
initializers. We disable it for all but address space 0 by default,
NVPTX and AMDGPU targets allow all but address space 3.

Diff Detail

Unit TestsFailed

Event Timeline

jdoerfert created this revision.Sep 6 2021, 2:05 PM
jdoerfert requested review of this revision.Sep 6 2021, 2:05 PM
Herald added a project: Restricted Project. · View Herald TranscriptSep 6 2021, 2:05 PM
Herald added a subscriber: wdng. · View Herald Transcript
jdoerfert updated this revision to Diff 370968.Sep 6 2021, 2:05 PM

clang format

tra added a comment.Sep 7 2021, 9:53 AM

For NVPTX, it's the __shared__ AS that's the odd one. Static initializers do work for __device__ and __constant__ globals.
I think this may be something we should plumb via TTI with AS(0) being the only AS allowed by default.

jdoerfert updated this revision to Diff 371148.Sep 7 2021, 12:24 PM

Introduce TTI hook

jdoerfert edited the summary of this revision. (Show Details)Sep 7 2021, 12:27 PM
tra added inline comments.Sep 7 2021, 1:43 PM
llvm/lib/Target/NVPTX/NVPTXTargetTransformInfo.h
52

While we should not have globals with ADDRESS_SPACE_LOCAL or ADDRESS_SPACE_PARAM, it may be worth to return false for them, too.

llvm/test/Transforms/GlobalOpt/address_space_initializer.ll
1

You may want to add another run for NVPTX with non-default AS and check that we do create the initializer.

jdoerfert updated this revision to Diff 371190.Sep 7 2021, 2:25 PM
jdoerfert edited the summary of this revision. (Show Details)

Better test coverage, added assertion

jdoerfert marked 2 inline comments as done.Sep 7 2021, 2:25 PM
jdoerfert added inline comments.
llvm/lib/Target/NVPTX/NVPTXTargetTransformInfo.h
52

That sounds to me more like an assertion. I'll add one for now, you let me know if that is ok too.

tra added inline comments.Sep 7 2021, 2:43 PM
llvm/lib/Target/NVPTX/NVPTXTargetTransformInfo.h
52

Assertions are for compiler programming errors, not for diagnosing invalid user-provided input.
Considering that one can write IR with a global var in an invalid AS I think assertion is not the right choice here.
An error would be more appropriate, IMO.

jdoerfert marked an inline comment as done.Sep 7 2021, 3:11 PM
jdoerfert added inline comments.
llvm/lib/Target/NVPTX/NVPTXTargetTransformInfo.h
52

TBH, I think such an input is broken and the verifier should trigger, which it does not: https://godbolt.org/z/xr1v361Wo
Assuming the IR is "valid" we should not misuse this interface with an AS that is not allowed for globals, IMHO.
That said, I'm not even sure what "an error" would look like here.

tra added inline comments.Sep 7 2021, 3:38 PM
llvm/lib/Target/NVPTX/NVPTXTargetTransformInfo.h
52

Right. TTI just does not have enough context to tell whether this particular call indicates a problem. Perhaps the best we can do here is to just provide the answer whether the AS can/can't handle global initializers and leave it up to the callers to deal with overall IR correctness.

In this particular patch, returning false for local/param AS would be valid. It will block the optimization and that would the the correct action regardless of soundness of the IR we're optimizing. Improving target-specific IR checks in the verifier would be nice, but it's beyond the scope of this patch and should be done separately.

arsenm added inline comments.Sep 7 2021, 4:32 PM
llvm/lib/Target/AMDGPU/AMDGPUTargetTransformInfo.h
187

Should also disallow REGION_ADDRESS, and PRIVATE_ADDRESS (we don't even allow private globals)

jdoerfert updated this revision to Diff 371458.Sep 8 2021, 3:05 PM

Return false for nonsensical address spaces

tra accepted this revision.Sep 8 2021, 3:19 PM
tra added inline comments.
llvm/lib/Target/NVPTX/NVPTXTargetTransformInfo.h
52

Nit: Making it a switch and enumerating all known AS would make it harder to give a wrong answer if/when a new AS is added.

This revision is now accepted and ready to land.Sep 8 2021, 3:19 PM
jdoerfert added inline comments.Sep 8 2021, 3:37 PM
llvm/lib/Target/NVPTX/NVPTXTargetTransformInfo.h
52

The AMD enum has dozens of members :( and we already do these checks in other places. I'd leave it like this for now if it's ok.

tra added inline comments.Sep 8 2021, 3:41 PM
llvm/lib/Target/NVPTX/NVPTXTargetTransformInfo.h
52

OK. This is fine, too.

arsenm added inline comments.Sep 15 2021, 7:58 AM
llvm/include/llvm/Analysis/TargetTransformInfoImpl.h
109

I'm not sure this should be so strict by default. At the minimum it should probably allow the datalayout's default global address space

jdoerfert added inline comments.Sep 15 2021, 8:06 AM
llvm/include/llvm/Analysis/TargetTransformInfoImpl.h
109

I have no strong feelings either way. This seems more cautious and maybe we want targets to overwrite it explicitly? That said, feel free to patch it.