Arthur Eubanks e42234383e Make DiagnosticInfoResourceLimit's limit param required
And always print it.

This makes some LLVM diagnostics match up better with Clang's diagnostics.

Updated some AMDGPU uses of DiagnosticInfoResourceLimit and now we print
better diagnostics for those.

Reviewed By: dblaikie

Differential Revision: https://reviews.llvm.org/D110204
2021-09-21 15:27:58 -07:00
..
2021-02-17 16:01:32 -08:00
2020-08-09 20:50:30 +02: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-08-05 12:36:26 -07:00
2020-08-05 12:36:26 -07:00
2020-06-15 16:18:05 -07:00
2021-02-17 16:01:32 -08:00
2020-06-15 16:18:05 -07:00
2021-01-21 10:51:36 -05:00
2021-02-17 16:01:32 -08:00
2021-08-25 09:50:59 -07:00
2021-02-17 16:01:32 -08:00
2021-02-17 16:01:32 -08: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.