| tag | daa9b842ba49bed97adc36c401e511d884091c92 | |
|---|---|---|
| tagger | Tobias Hieta <tobias@hieta.se> | Tue Nov 14 10:07:56 2023 +0100 |
| object | 98bfdac5ce82d1679f8af9a57501471812ab68d7 |
LLVM 17.0.5 Release
| commit | 98bfdac5ce82d1679f8af9a57501471812ab68d7 | [log] [tgz] |
|---|---|---|
| author | Nikita Popov <npopov@redhat.com> | Thu Nov 09 10:23:10 2023 +0100 |
| committer | Tobias Hieta <tobias@hieta.se> | Tue Nov 14 09:22:39 2023 +0100 |
| tree | 35c47da3874fee2de0ecb1da1a7acef08710924b | |
| parent | 12c6ee8fd2046c85ae9693105288fcd749b90733 [diff] |
[BranchFolding] Remove dubious assert from operator< (#71639) `MergePotentialElts::operator<` asserts that the two elements being compared are not equal. However, sorting functions are allowed to invoke the comparison function with equal arguments (though they usually don't for efficiency reasons). There is an existing special-case that disables the assert if _GLIBCXX_DEBUG is used, which may invoke the comparator with equal args to verify strict weak ordering. I believe libc++ also has strict weak ordering checks under some options nowadays. Recently, #71312 was reported, where a change to glibc's qsort_r implementation can also result in comparison between equal elements. From what I understood, this is an inefficiency that will be fixed on the glibc side as well, but I think at this point we should just remove this assertion. Fixes https://github.com/llvm/llvm-project/issues/71312. (cherry picked from commit 74a76a288562c486f377121855ef7db0386e0e43)
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, or #llvm IRC channel on OFTC.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.