4 Commits

Author	SHA1	Message	Date
Sebastian Neubauer	4359b870b1	[AMDGPU] Init scratch only if necessary ... If no scratch or flat instructions are used, we do not need to initialize the flat scratch hardware register. Differential Revision: https://reviews.llvm.org/D105920	2021-07-14 10:45:22 +02:00
Stanislav Mekhanoshin	6fb02596a2	[AMDGPU] Add support for architected flat scratch ... Add support for the readonly flat Scratch register initialized by the SPI. Differential Revision: https://reviews.llvm.org/D102432	2021-05-14 10:53:48 -07:00
Stanislav Mekhanoshin	eb66bf0802	[AMDGPU] Print SCRATCH_EN field after the kernel ... Differential Revision: https://reviews.llvm.org/D93353	2020-12-15 22:44:30 -08:00
Matt Arsenault	21d2884a9c	AMDGPU: Annotate functions that have stack objects ... Relying on any MachineFunction state in the MachineFunctionInfo constructor is hazardous, because the construction time is unclear and determined by the first use. The function may be only partially constructed, which is part of why we have many of these hacky string attributes to track what we need for ABI lowering. For SelectionDAG, all stack objects are created up-front before calling convention lowering so stack objects are visible at construction time. For GlobalISel, none of the IR function has been visited yet and the allocas haven't been added to the MachineFrameInfo yet. This should fix failing to set flat_scratch_init in GlobalISel when needed. This pass really needs to be turned into some kind of analysis, but I haven't found a nice way use one here.	2020-05-19 18:51:00 -04:00