We have a code of conduct encouraging various behaviours, especially being welcoming and patient with newcomers. We also have a statement that AI contributions are acceptable provided the contributor understands the code before submitting for review. These interact in an unfortunate fashion. I’m posting this after seeing Gentoo’s AI policy Gentoo AI Policy | Hacker News , specifically comments from a newcomer to llvm: I’ve been using AI to contribute to LLVM, which has a liberal policy....| LLVM Discussion Forums
[RFC] Ripple: A Compiler-Interpreted API for Efficient SIMD Programming TL;DR We have been working on Ripple, a lean addition to LLVM to support Single-Program, Multiple-Data (SPMD) and loop-annotation-based parallel programming for SIMD hardware. We propose a parallel programming API to support these two models, which departs from GPU-style SPMD programming, in that block computations of different dimensions (including 0) can coexist in the same function. This makes it easier to explicitly e...| 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
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
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
