Files
clang-p2996/llvm/test/CodeGen/AMDGPU
Arthur Eubanks 8815ce03e8 Remove "Rewrite Symbols" from codegen pipeline
It breaks up the function pass manager in the codegen pipeline.

With empty parameters, it looks at the -mllvm flag -rewrite-map-file.
This is likely not in use.

Add a check that we only have one function pass manager in the codegen
pipeline.

Some tests relied on the fact that we had a module pass somewhere in the
codegen pipeline.

addr-label.ll crashes on ARM due to this change. This is because a
ARMConstantPoolConstant containing a BasicBlock to represent a
blockaddress may hold an invalid pointer to a BasicBlock if the
blockaddress is invalidated by its BasicBlock getting removed. In that
case all referencing blockaddresses are RAUW a constant int. Making
ARMConstantPoolConstant::CVal a WeakVH fixes the crash, but I'm not sure
that's the right fix. As a workaround, create a barrier right before
ISel so that IR optimizations can't happen while a
ARMConstantPoolConstant has been created.

Reviewed By: rnk, MaskRay, compnerd

Differential Revision: https://reviews.llvm.org/D99707
2021-05-31 08:32:36 -07:00
..
2021-02-17 16:01:32 -08:00
2019-05-08 22:09:57 +00:00
2017-08-07 18:30:35 +00:00
2020-08-09 20:50:30 +02:00
2017-08-07 18:30:35 +00:00
2020-08-09 20:50:30 +02:00
2021-02-17 16:01:32 -08:00
2019-03-19 15:50:24 +00:00
2019-07-01 17:17:45 +00:00
2021-02-17 16:01:32 -08:00
2021-02-17 16:01:32 -08:00
2021-02-17 16:01:32 -08:00
2020-06-15 16:18:05 -07:00
2019-03-19 15:50:24 +00:00
2019-04-26 16:37:51 +00:00
2021-02-17 16:01:32 -08:00
2019-03-19 15:50:24 +00:00
2021-02-17 16:01:32 -08:00
2015-06-13 03:28:10 +00:00
2021-01-21 10:51:36 -05:00
2021-02-17 16:01:32 -08:00
2018-06-27 15:33:33 +00:00
2020-08-09 20:50:30 +02:00
2020-06-25 10:38:23 +02:00
2020-08-09 20:50:30 +02:00
2020-08-09 20:50:30 +02:00
2021-05-05 18:41:18 -04:00
2021-02-17 16:01:32 -08:00
2019-05-03 15:37:07 +00:00
2021-02-17 16:01:32 -08:00
2020-04-03 10:07:21 +01:00
2020-08-09 20:50:30 +02:00
2020-06-15 16:18:05 -07:00
2020-08-09 20:50:30 +02:00
2021-03-15 21:44:15 +09: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.