llvm-project
llvm-project copied to clipboard
llvm
The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
Not sure if this is a bug or if we do things incorrectly. Compiling bc code with llc to target Apple M1 ```shell clang+llvm-15.0.2-arm64-apple-darwin21.0/bin/llc --mtriple=arm64-apple-darwin20.1.0 -march=arm64 -mcpu=apple-m1 --relocation-model=pic -O0 -filetype=obj...
Link for opt trunk: General Alive proof for divisor small enough to avoid addition overflow: Given an input like ```llvm %_4 = urem i32 %x, 13 %_6 = urem i32...
`objcopy -O binary` produces a broken binary from the [test.elf](https://github.com/llvm/llvm-project/files/9800058/test.zip) file. Regressed version: ```shell $ rust-objcopy -V llvm-objcopy, compatible with GNU objcopy LLVM (http://llvm.org/): LLVM version 15.0.2-rust-1.66.0-nightly Optimized build. Default...
```cpp #include void foo() { std::error_code ec; } ``` The code does get optimized away as system_category() is [[gnu::const]] but there is no -Wunused warning. https://godbolt.org/z/M68ToY78b
test case https://gcc.godbolt.org/z/5dTff475M ``` unsigned __int128 mul64 (unsigned __int128 mul0, unsigned __int128 mul1) { return (mul0 & 0xffffffffffffffff) * (mul1 & 0xffffffffffffffff); } ``` * llvm has a redundant mov...
[ASan] Feature request: Allow ignoring some new-delete-type-mismatch without disabling it altogether
I want to analyze my application code for **new-delete-type-mismatch** issues, with AddressSanitizer. However, in order to do this, first I'd like to disable such reports from 3rd-party code and focus...
MLIR's async runtime uses atomics: https://github.com/llvm/llvm-project/blob/d86a206f06a51c12a9fcf2c20199f4e819751c0c/mlir/lib/ExecutionEngine/AsyncRuntime.cpp#L76 but appears not to link against `libatomic` on arch that require it: https://github.com/llvm/llvm-project/blob/d86a206f06a51c12a9fcf2c20199f4e819751c0c/mlir/lib/ExecutionEngine/CMakeLists.txt#L139-L147 Resulting in unresolved symbols when building ie for armv6: ``` undefined...
Using llvm 15.0.2 (or 14.0.6) compiling code that uses 128 bit integers (with either -fforce-enable-int128 or using MODE TI types) and targeting Cortex-M55 or Cortex-M85 crashes with an Optimizer error...
When using `scf::tileConsumerAndFuseProducerGreedilyUsingSCFForOp` to tile and fuse `linalg.matmul` with `linalg.fill`, it doesn't keep `linalg.fill` outside the reduction loop, which results in incorrect result. This can be reproduced with https://github.com/pzread/llvm-project/commit/9ea44bdee2f0b47289f80061248c88223c0c99ab. In...
``` Stack dump: 0. Program arguments: c:\\users\\omair\\work\\llvm-dev\\build\\bin\\llc.exe -mtriple=aarch64-pc-windows-msvc -O0 -filetype=obj -o C:\\Users\\omair\\work\\llvm-dev\\build\\test\\DebugInfo\\ARM\\Output\\split-complex.ll.tmp.o C:\\Users\\omair\\work\\llvm-dev\\llvm-project\\llvm\\test\\DebugInfo\\ARM\\split-complex.ll 1. Running pass 'Function Pass Manager' on module 'C:\Users\omair\work\llvm-dev\llvm-project\llvm\test\DebugInfo\ARM\split-complex.ll'. 2. Running pass 'IRTranslator' on function '@f' Exception...
