Oliver Stannard 9ed9eb72f4 Refactor backend diagnostics for unsupported features
Re-commit of r258951 after fixing layering violation.

The BPF and WebAssembly backends had identical code for emitting errors
for unsupported features, and AMDGPU had very similar code. This merges
them all into one DiagnosticInfo subclass, that can be used by any
backend.

There should be minimal functional changes here, but some AMDGPU tests
have been updated for the new format of errors (it used a slightly
different format to BPF and WebAssembly). The AMDGPU error messages will
now benefit from having precise source locations when debug info is
available.



git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@259498 91177308-0d34-0410-b5e6-96231b3b80d8
2016-02-02 13:52:43 +00:00
..
2016-01-18 22:01:13 +00:00
2016-01-26 00:03:25 +00:00
2016-01-22 18:42:38 +00:00
2016-01-28 20:53:35 +00:00
2016-01-08 14:50:23 +00:00
2015-11-24 12:18:54 +00:00
2016-01-29 10:05:16 +00:00
2015-12-19 01:39:48 +00:00
2015-12-19 01:39:48 +00:00
2016-01-18 22:09:04 +00:00
2016-01-18 22:01:13 +00:00
2016-01-18 22:09:04 +00:00
2016-01-11 17:02:10 +00:00
2016-01-28 20:53:42 +00:00
2016-01-18 22:09:04 +00:00
2015-11-24 12:18:54 +00:00
2015-10-29 15:05:03 +00:00
2016-01-11 21:18:40 +00:00
2015-10-20 03:59:58 +00:00
2016-01-28 20:53:42 +00: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.