llvm-project.git/llvm/test/CodeGen/PowerPC/func-alias.ll, branch users/nico/python-2 Unnamed repository; edit this file 'description' to name the repository. [PowerPC] Convert more tests to opaque pointers (NFC) 2023-01-30T01:27:10+00:00 Sergei Barannikov barannikov88@gmail.com 2023-01-29T23:59:37+00:00 f4fbcd62af31ac8921c2c2216bdbed1b49a0dff1 * Add -fast-isel=false to func-alias.ll. The test was added as a SelectionDAG test. Without this option, FastISel successfully selects the call that had a ConstantExpr argument. * fast-isel-branch.ll couldn't be handled by FastISel. Now it can, hence the change in the stack offsets. 
* Add -fast-isel=false to func-alias.ll. The test was added as a
SelectionDAG test. Without this option, FastISel successfully selects
the call that had a ConstantExpr argument.
* fast-isel-branch.ll couldn't be handled by FastISel. Now it can,
hence the change in the stack offsets.
[AsmParser] Remove typed pointer auto-detection 2023-01-18T08:58:32+00:00 Nikita Popov npopov@redhat.com 2022-12-14T12:41:10+00:00 9ed2f14c87174e316de03407442eed2c643f3695 IR is now always parsed in opaque pointer mode, unless -opaque-pointers=0 is explicitly given. There is no automatic detection of typed pointers anymore. The -opaque-pointers=0 option is added to any remaining IR tests that haven't been migrated yet. Differential Revision: https://reviews.llvm.org/D141912 
IR is now always parsed in opaque pointer mode, unless
-opaque-pointers=0 is explicitly given. There is no automatic
detection of typed pointers anymore.

The -opaque-pointers=0 option is added to any remaining IR tests
that haven't been migrated yet.

Differential Revision: https://reviews.llvm.org/D141912
[PowerPC] Fix for PC Relative call protocol 2020-07-01T12:08:41+00:00 Stefan Pintilie stefanp@ca.ibm.com 2020-07-01T12:08:41+00:00 b294e00fb079600f337f479eb29fc27058228302 The situation where the caller uses a TOC and the callee does not but is marked as clobbers the TOC (st_other=1) was not being compiled correctly if both functions where in the same object file. The call site where we had `callee` was missing a nop after the call. This is because it was assumed that since the two functions where in the same DSO they would be sharing a TOC. This is not the case if the callee uses PC Relative because in that case it may clobber the TOC. This patch makes sure that we add the cnop correctly so that the linker has a place to restore the TOC. Reviewers: sfertile, NeHuang, saghir Differential Revision: https://reviews.llvm.org/D81126 
The situation where the caller uses a TOC and the callee does not
but is marked as clobbers the TOC (st_other=1) was not being compiled
correctly if both functions where in the same object file.

The call site where we had `callee` was missing a nop after the call.
This is because it was assumed that since the two functions where in
the same DSO they would be sharing a TOC. This is not the case if the
callee uses PC Relative because in that case it may clobber the TOC.
This patch makes sure that we add the cnop correctly so that the
linker has a place to restore the TOC.

Reviewers: sfertile, NeHuang, saghir

Differential Revision: https://reviews.llvm.org/D81126