Profile - nikic - LLVM Discussion Forums
A place to discuss both usage and development of the LLVM project.| LLVM Discussion Forums
A place to discuss both usage and development of the LLVM project.| LLVM Discussion Forums
Replace address computation of TLS variables, not access, but yes. It does solve it, by making that IR not possible to write. In my not-really-fleshed-out idea here, @x should no longer be usable as a pointer, so i32* @x is impossible to write in IR – which is as it should be. You need an Instruction to retrieve the address for @x, and thus it’s clearly impossible to use in a global value initializer. Perhaps @x has become a token type of some sort, which can be passed to the intrinsic bu...| LLVM Discussion Forums
5 years ago, @nikic wrote: I can’t say a 10% improvement is making LLVM fast again, we would need a 10x improvement for it to deserve that label. We recently open-sourced TPDE and our fast LLVM baseline back-end (TPDE-LLVM), which is 10-20x faster than the LLVM -O0 back-end with similar runtime performance and 10-30% larger code size. We support a typical subset of LLVM-IR and only target x86-64 and AArch64. Posting this here, as this might be interesting for the LLVM community – question...| LLVM Discussion Forums
Hi! I am looking for a little input. The context is that I am trying to reduce the size of our arm64 (elf) executable. We can’t afford to lower the optimisation level due to performance targets, but we already do the following to keep exe sizes down: visibility=hidden We use a PGO profile ThinLTO data/function sections and gc-sections We don’t use RTTI/exceptions Enabled ICF in lld Is there something I am missing? I have searched through the forums and there has been talk about a machine ...| LLVM Discussion Forums
I’ve just submitted ⚙ D154014 [SpecialCaseList] Use Globs instead of Regex for review which is a breaking change for special case lists (SCL) that greatly improves their usability. Here are the users of SCL that I could find: Sanitizers (AddressSanitizer, ThreadSanitizer, MemorySanitizer, DataFlowSanitizer) Clang and LLVM instrumentation XRay sancov llvm-cov The hope is that most of these uses only need to specify simple source files (*/src/foo.{c,cpp}) or functions (*_unsafe_*) which are...| LLVM Discussion Forums
This is a joint proposal from: @AaronBallman, @shafik, @Endill, and @cor3ntin (with helpful input from others!) Safety and security of C and C++ programs has been an important issue in the ecosystem for a while. Both WG21 and WG14 are making plans on how to improve these aspects of the language from their end, but the standard is constrained by what it can talk about and the speed at which it can move. Implementations need to be the driving force behind improving this situation; we’re ultim...| LLVM Discussion Forums
A place to discuss both usage and development of the LLVM project.| LLVM Discussion Forums
Authors: Owen Anderson, Jessica Clarke, Alex Richardson, David Chisnall This RFC is a proposal to gain consensus on upstreaming target support for the CHERI-enabled architectures to the LLVM project. This is an “entire project” RFC, as CHERI support touches many parts of the toolchain: primarily LLVM, Clang, and LLD, with other components such as runtime libraries or LLDB potentially being touched as well. Upstreaming many of these sub-components of CHERI support will likely merit their o...| LLVM Discussion Forums
Hello all, The HLSL compiler community is interested in contributing HLSL, DirectX and Vulkan graphics support to Clang and LLVM. Why do we want to do this? The existing HLSL compiler, the DirectX Shader Compiler (DXC), is a fork of LLVM/Clang 3.7 and is developed open source on GitHub (https://github.com/microsoft/DirectXShaderCompiler) by Microsoft and a diverse community of open source partners. We plan to update our compiler to the latest LLVM. This plan is motivated by our efforts to bri...| LLVM Discussion Forums
