rust/compiler/rustc_llvm/llvm-wrapper
Simonas Kazlauskas 487e27350a Don't set `fast`(-math) for certain simd ops
`fast-math` implies things like functions not being able to accept as an
argument or return as a result, say, `inf` which made these functions
confusingly named or behaving incorrectly, depending on how you
interpret it. Since the time when these intrinsics have been implemented
the intrinsics user's (stdsimd) approach has changed significantly and
so now it is required that these intrinsics operate normally rather than
in "whatever" way.

Fixes #84268
2021-04-17 23:33:10 +03:00
..
.editorconfig Move `rustllvm` into `rustc_llvm` 2020-09-09 23:05:43 +03:00
ArchiveWrapper.cpp Update the minimum external LLVM to 10 2021-03-22 11:33:43 -07:00
CoverageMappingWrapper.cpp fix: I meant LLVM version 13, not 12 2021-03-19 16:46:40 -04:00
LLVMWrapper.h LLVMWrapper: attractive nuisance macros 2021-03-24 14:39:13 -04:00
Linker.cpp Move `rustllvm` into `rustc_llvm` 2020-09-09 23:05:43 +03:00
PassWrapper.cpp Categorize and explain target features support 2021-04-09 10:16:04 -05:00
README Move `rustllvm` into `rustc_llvm` 2020-09-09 23:05:43 +03:00
RustWrapper.cpp Don't set `fast`(-math) for certain simd ops 2021-04-17 23:33:10 +03:00

README

This directory currently contains some LLVM support code. This will generally
be sent upstream to LLVM in time; for now it lives here.

NOTE: the LLVM C++ ABI is subject to between-version breakage and must *never*
be exposed to Rust. To allow for easy auditing of that, all Rust-exposed types
must be typedef-ed as "LLVMXyz", or "LLVMRustXyz" if they were defined here.

Functions that return a failure status and leave the error in
the LLVM last error should return an LLVMRustResult rather than an
int or anything to avoid confusion.

When translating enums, add a single `Other` variant as the first
one to allow for new variants to be added. It should abort when used
as an input.

All other types must not be typedef-ed as such.