This is an archive of the discontinued LLVM Phabricator instance.

TTI: Add addrspace parameters to memcpy lowering functions
ClosedPublic

Authored by arsenm on Feb 14 2020, 1:30 PM.

Details

Summary

Not sure whether the alignment/addrspace parameters should be grouped together instead

Diff Detail

Event Timeline

arsenm created this revision.Feb 14 2020, 1:30 PM
Herald added a project: Restricted Project. · View Herald TranscriptFeb 14 2020, 1:30 PM

To me the grouping that you have here makes the most sense, but I don't have a strong opinion either way.

Is the idea with this that you can override the types used for the mempy based on either the source or destination address space? If not, why is the address space needed (out of curiosity)?

arsenm added a comment.Mar 4 2020, 9:29 AM

To me the grouping that you have here makes the most sense, but I don't have a strong opinion either way.

Is the idea with this that you can override the types used for the mempy based on either the source or destination address space? If not, why is the address space needed (out of curiosity)?

Yes. Any query that involves memory that doesn't have an address space ends up being a problem eventually. For AMDGPU we would prefer to use wider accesses for certain address spaces

jdoerfert accepted this revision.Mar 16 2020, 10:34 AM

LGTM. (this is NFC and makes sense)

This revision is now accepted and ready to land.Mar 16 2020, 10:34 AM