Sameer Sahasrabuddhe 179ed88711 [AAPointerInfo] handle multiple offsets in PHI
Previously reverted in 12696d302d146ffe616eecab3feceba9d29be2db

The arguments to a PHI may represent a recurrence by eventually using the output
of the PHI itself. This is now handled by checking for cycles in the control
flow. If a PHI is not in a recurrence, it is now able to report multiple offsets
instead of conservatively reporting unknown.

Reviewed By: jdoerfert

Differential Revision: https://reviews.llvm.org/D138991
2022-12-15 12:23:50 +05:30
..
2022-12-14 15:57:56 +00:00
2022-07-08 09:13:59 +01:00
2022-07-08 09:13:59 +01:00
2022-12-13 10:34:26 -05:00
2022-12-13 10:34:26 -05:00
2022-12-07 22:02:54 +00:00
2022-07-08 09:13:59 +01:00
2022-12-07 22:02:54 +00:00
2022-07-08 09:13:59 +01:00
2021-11-30 15:00:16 +01:00
2022-07-08 09:13:59 +01:00
2022-07-08 09:13:59 +01:00
2022-07-08 09:13:59 +01:00
2022-11-04 15:49:37 -07:00
2022-07-08 09:13:59 +01:00
2022-07-08 09:13:59 +01:00
2022-12-07 10:23:52 +01:00
2022-12-07 10:23:52 +01:00
2022-12-07 10:23:52 +01:00
2022-12-07 10:23:52 +01:00
2022-12-07 10:23:52 +01:00
2022-07-08 09:13:59 +01:00
2022-11-30 18:02:39 +00:00
2022-07-08 09:13:59 +01:00
2022-07-08 09:13:59 +01:00

+==============================================================================+
| How to organize the lit tests                                                |
+==============================================================================+

- If you write a test for matching a single DAG opcode or intrinsic, it should
  go in a file called {opcode_name,intrinsic_name}.ll (e.g. fadd.ll)

- If you write a test that matches several DAG opcodes and checks for a single
  ISA instruction, then that test should go in a file called {ISA_name}.ll (e.g.
  bfi_int.ll

- For all other tests, use your best judgement for organizing tests and naming
  the files.

+==============================================================================+
| Naming conventions                                                           |
+==============================================================================+

- Use dash '-' and not underscore '_' to separate words in file names, unless
  the file is named after a DAG opcode or ISA instruction that has an
  underscore '_' in its name.