From: Chris Lattner Date: Sun, 27 Nov 2011 19:38:20 +0000 (+0000) Subject: rewrite the known problems section. Including a short list of individual bugs per... X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=70e22016281508228a21dad6314ec96229af85d9;p=oota-llvm.git rewrite the known problems section. Including a short list of individual bugs per target isn't particularly useful. Link to the target features matrix. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@145193 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index ca00a454afe..7568575d9be 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -1330,144 +1330,30 @@ compiler and provides better integration with the platform ABI as a result.

-

This section contains significant known problems with the LLVM system, listed - by component. If you run into a problem, please check - the LLVM bug database and submit a bug if - there isn't already one.

- - -

- Experimental features included with this release -

- -
- -

The following components of this LLVM release are either untested, known to - be broken or unreliable, or are in early development. These components - should not be relied on, and bugs should not be filed against them, but they - may be useful to some people. In particular, if you would like to work on - one of these components, please contact us on - the LLVMdev - list.

- -
    -
  • The Alpha, Blackfin, CellSPU, MicroBlaze, MSP430, MIPS, PTX, SystemZ and - XCore backends are experimental.
  • - -
  • llc "-filetype=obj" is experimental on all targets other - than darwin and ELF X86 systems.
  • -
- -
- - -

- Known problems with the X86 back-end -

- -
- - - -
- - -

- Known problems with the PowerPC back-end -

- -
- -
    -
  • The PPC32/ELF support lacks PIC support.
  • -
- -
- - -

- Known problems with the ARM back-end -

- -
- -
    -
  • Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6 - processors, thumb programs can crash or produce wrong results - (PR1388).
  • - -
  • Compilation for ARM Linux OABI (old ABI) is supported but not fully - tested.
  • -
- -
- - -

- Known problems with the SPARC back-end -

- -
- -
    -
  • The SPARC backend only supports the 32-bit SPARC ABI (-m32); it does not - support the 64-bit SPARC ABI (-m64).
  • -
- -
- - -

- Known problems with the MIPS back-end -

- -
- -
    -
  • 64-bit MIPS targets are not supported yet.
  • -
- -
- - -

- Known problems with the Alpha back-end -

- -
- -
    -
  • On 21164s, some rare FP arithmetic sequences which may trap do not have - the appropriate nops inserted to ensure restartability.
  • -
- -
- - -

- Known problems with the C back-end -

- -
- -

The C backend has numerous problems and is not being actively maintained. - Depending on it for anything serious is not advised.

- +

LLVM is generally a production quality compiler, and is used by a broad range + of applications and shipping in many products. That said, not every + subsystem is as mature as the aggregate, particularly the more obscure + targets. If you run into a problem, please check the LLVM bug database and submit a bug if + there isn't already one or ask on the LLVMdev + list.

+ +

Known problem areas include:

+
    -
  • The C backend has only basic support for - inline assembly code.
  • - -
  • The C backend violates the ABI of common - C++ programs, preventing intermixing between C++ compiled by the CBE - and C++ code compiled with llc or native compilers.
  • - -
  • The C backend does not support all exception handling constructs.
  • - -
  • The C backend does not support arbitrary precision integers.
  • +
  • The Alpha, Blackfin, CellSPU, MSP430, PTX, SystemZ and + XCore backends are experimental, and several of these have already been + removed from mainline.
  • + +
  • The integrated assembler, disassembler, and JIT is not supported by + several targets. If an integrated assembler is not supported, then a + system assembler is required. For more details, see the Target Features Matrix. +
  • + +
  • The C backend has numerous problems and is not being actively maintained. + Depending on it for anything serious is not advised.