llvm-project.git/llvm/lib/CodeGen/InterleavedLoadCombinePass.cpp, branch users/nico/python-2 Unnamed repository; edit this file 'description' to name the repository. [CodeGen] Remove unused includes (NFC) (#115996) 2024-11-13T07:15:06+00:00 Kazu Hirata kazu@google.com 2024-11-13T07:15:06+00:00 735ab61ac828bd61398e6847d60e308fdf2b54ec Identified with misc-include-cleaner. 
Identified with misc-include-cleaner.
 [IR] Add getDataLayout() helpers to Function and GlobalValue (#96919) 2024-06-28T06:36:49+00:00 Nikita Popov npopov@redhat.com 2024-06-28T06:36:49+00:00 9df71d7673b5c98e1032d01be83724a45b42fafc Similar to https://github.com/llvm/llvm-project/pull/96902, this adds `getDataLayout()` helpers to Function and GlobalValue, replacing the current `getParent()->getDataLayout()` pattern. 
Similar to https://github.com/llvm/llvm-project/pull/96902, this adds
`getDataLayout()` helpers to Function and GlobalValue, replacing the
current `getParent()->getDataLayout()` pattern.
 InterleavedLoadCombine: Correctly query PM for TargetTransformInfo (#93103) 2024-05-23T05:07:16+00:00 Matt Arsenault Matthew.Arsenault@amd.com 2024-05-23T05:07:16+00:00 7f5c71efc441083282a5365d245acfe6afcd0dd5 






[InterleavedLoadCombine] Bail out on non-byte-sized vector element type (#90705)
2024-05-02T00:38:09+00:00

Nikita Popov
npopov@redhat.com

2024-05-02T00:38:09+00:00

d484c4d3501a7ff3d00a6e0cfad026a3b01d320c

Vectors are always tightly packed, and elements of non-byte-sized
usually do not have a well-defined (byte) offset.

Fixes https://github.com/llvm/llvm-project/issues/90695.




Vectors are always tightly packed, and elements of non-byte-sized
usually do not have a well-defined (byte) offset.

Fixes https://github.com/llvm/llvm-project/issues/90695.






[CodeGen] Remove extraneous ArrayRef (NFC) (#90423)
2024-04-29T23:30:57+00:00

Kazu Hirata
kazu@google.com

2024-04-29T23:30:57+00:00

ae7ce1c6e728a262049c998c667b79165b285bd8

We don't need to explicitly create an instance of ArrayRef here
because getIndexedOffsetInType takes ArrayRef, and ArrayRef can be
implicitly constructed from a C array.




We don't need to explicitly create an instance of ArrayRef here
because getIndexedOffsetInType takes ArrayRef, and ArrayRef can be
implicitly constructed from a C array.






[CodeGen] Port `InterleavedLoadCombine` to new pass manager (#75164)
2023-12-13T04:46:22+00:00

paperchalice
liujunchang97@outlook.com

2023-12-13T04:46:22+00:00

a930fec033a80bc92f5a11cc334ff4fc44cbe0ca












[llvm] Replace calls to Type::getPointerTo (NFC)
2023-11-27T16:49:34+00:00

Youngsuk Kim
youngsuk.kim@hpe.com

2023-11-27T16:36:38+00:00

d8b8aa3a56611477f93d029a59a0b350fb5166b0

Cleanup work towards removing the method Type::getPointerTo.

If a call to Type::getPointerTo is used solely to support an unneeded
pointer-cast, remove the call entirely.





Cleanup work towards removing the method Type::getPointerTo.

If a call to Type::getPointerTo is used solely to support an unneeded
pointer-cast, remove the call entirely.







[llvm] Fix duplicate word typos. NFC
2023-09-02T01:25:16+00:00

Fangrui Song
i@maskray.me

2023-09-02T01:25:16+00:00

111fcb0df02db3db8bed1d5db6d911b7ce544d92

Those fixes were taken from https://reviews.llvm.org/D137338





Those fixes were taken from https://reviews.llvm.org/D137338







[CodeGen] Disable default copy assignment operator for struct VectorInfo
2023-06-07T06:32:56+00:00

Bing1 Yu
bing1.yu@intel.com

2023-06-07T06:32:36+00:00

2b09c50f69b79470d19e3621c4f526b9d81af306

struct VectorInfo manages resources such as dynamically allocated memory, it's generally a good practice to either implement a custom copy constructor or disable the default one

Reviewed By: kazu

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





struct VectorInfo manages resources such as dynamically allocated memory, it's generally a good practice to either implement a custom copy constructor or disable the default one

Reviewed By: kazu

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







Use APInt::count{l,r}_{zero,one} (NFC)
2023-02-20T06:04:47+00:00

Kazu Hirata
kazu@google.com

2023-02-20T06:04:47+00:00

f8f3db27565cae8e07c2487f9714a32840c6d548