llvm-project.git/llvm/test/CodeGen/SystemZ/stack-guard.ll, branch users/nico/python-2 Unnamed repository; edit this file 'description' to name the repository. [SystemZ][NFC] Opaque pointer migration. 2022-10-11T21:09:43+00:00 Kai Nacke kai.peter.nacke@ibm.com 2022-10-11T20:59:16+00:00 a1710eb3cd5823c5d14899112ca3086acbdbe9cb The LIT test cases were migrated with the script provided by Nikita Popov. No manual changes were made. Committed without review since no functional changes, after consultation with uweigand. 
The LIT test cases were migrated with the script provided by
Nikita Popov.

No manual changes were made. Committed without review since
no functional changes, after consultation with uweigand.
Use SETNE directly rather than SUB/SETNE 0 for stack guard check 2020-02-18T13:21:26+00:00 James Clarke jrtc27@jrtc27.com 2020-02-18T13:21:23+00:00 b3cd44f80b8d6de76d41f1c78241d782c77cd193 Summary: Backends should fold the subtraction into the comparison, but not all seem to. Moreover, on targets where pointers are not integers, such as CHERI, an integer subtraction is not appropriate. Instead we should just compare the two pointers directly, as this should work everywhere and potentially generate more efficient code. Reviewers: bogner, lebedev.ri, efriedma, t.p.northover, uweigand, sunfish Reviewed By: lebedev.ri Subscribers: dschuff, sbc100, arichardson, jgravelle-google, hiraditya, aheejin, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D74454 
Summary:
Backends should fold the subtraction into the comparison, but not all
seem to. Moreover, on targets where pointers are not integers, such as
CHERI, an integer subtraction is not appropriate. Instead we should just
compare the two pointers directly, as this should work everywhere and
potentially generate more efficient code.

Reviewers: bogner, lebedev.ri, efriedma, t.p.northover, uweigand, sunfish

Reviewed By: lebedev.ri

Subscribers: dschuff, sbc100, arichardson, jgravelle-google, hiraditya, aheejin, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D74454
Add address space mangling to lifetime intrinsics 2017-04-10T20:18:21+00:00 Matt Arsenault Matthew.Arsenault@amd.com 2017-04-10T20:18:21+00:00 f10061ec708ef787398649f3eb073c6ca3acd73d In preparation for allowing allocas to have non-0 addrspace. llvm-svn: 299876 
In preparation for allowing allocas to have non-0 addrspace.

llvm-svn: 299876
[SystemZ] [SSP] Add support for LOAD_STACK_GUARD. 2016-04-24T13:57:49+00:00 Marcin Koscielnicki koriakin@0x04.net 2016-04-24T13:57:49+00:00 aef3b5b5e2d8bcb321832859464ff11100811609 This fixes PR22248 on s390x. The previous attempt at this was D19101, which was before LOAD_STACK_GUARD existed. Compared to the previous version, this always emits a rather ugly block of 4 instructions, involving a thread pointer load that can't be shared with other potential users. However, this is necessary for SSP - spilling the guard value (or thread pointer used to load it) is counter to the goal, since it could be overwritten along with the frame it protects. Differential Revision: http://reviews.llvm.org/D19363 llvm-svn: 267340 
This fixes PR22248 on s390x.  The previous attempt at this was D19101,
which was before LOAD_STACK_GUARD existed.  Compared to the previous
version, this always emits a rather ugly block of 4 instructions, involving
a thread pointer load that can't be shared with other potential users.
However, this is necessary for SSP - spilling the guard value (or thread
pointer used to load it) is counter to the goal, since it could be
overwritten along with the frame it protects.

Differential Revision: http://reviews.llvm.org/D19363

llvm-svn: 267340