Hacker GitHub

← All repos

llvm/llvm-project

View on GitHub ↗ ★ 41,296 LLVM

The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.

319 mentions on Hacker News by 202 people: 30 stories, 289 comments · first 2019-03-20 · latest 2026-10-31

Mentions per year 319 mentions · busiest year 2025 (96)
20082026
AllStoriesComments NewestTopOldest
  1. …by C++ clang only related contributions instead of LLVM ones? Most likely not, only clicked here https://github.com/llvm/llvm-project/graphs/contributors and came right away to reply.
    comment by pjmlp · 2025-02-24 · in OpenBSD Innovations
  2. …own subsystems or putting down markers documenting how the subsystems are supposed to work. Maybe https://github.com/llvm/llvm-project/issues/74205 would help once it trickles down into the kernel, but I suspect that people are still going…
    comment by vlovich123 · 2025-02-18 · in I helped fix sleep-wake hangs on Linux with AMD GPUs
  3. > there's an open bug ticket noting that it doesn't protect against contraction ( https://github.com/llvm/llvm-project/issues/91674 ). Huh. ¯\_(ツ)_/¯ I didn't really mean the loop thing as much of a problem for the goal of reproducibility…
    comment by dzaima · 2025-02-13 · in Elementary Functions and Not Following IEEE754 Floating-Point Standard (2020)
  4. …though there's an open bug ticket noting that it doesn't protect against contraction ( https://github.com/llvm/llvm-project/issues/91674 ). Still worth trying though. I was aware of GCC __builtin_assoc_barrier, but it wasn't documented to…
    comment by AlotOfReading · 2025-02-13 · in Elementary Functions and Not Following IEEE754 Floating-Point Standard (2020)
  5. …//github.com/openzfs/zfs/commit/677c6f8457943fe5b56d7a... There is an open LLVM issue regarding this: https://github.com/llvm/llvm-project/issues/62790 The issue explains why __builtin_unpredictable() does not address the problem. In…
    comment by ryao · 2025-02-09 · in Don't "optimize" conditional moves in shaders with mix()+step()
  6. I'm excited about -fbounds-safety coming soon: https://github.com/llvm/llvm-project/commit/64360899c76c
    comment by 1over137 · 2025-02-01 · in Falsehoods programmers believe about null pointers
  7. okay can you at least tell me how the architecture of https://github.com/llvm/llvm-project is "bad"?
    comment by almostgotcaught · 2025-01-31 · in A better build system for OCaml
  8. …huh? since you fancy yourself an architect can you let me know how we might fix the architecture of https://github.com/llvm/llvm-project such that CMake is no longer needed?
    comment by almostgotcaught · 2025-01-31 · in A better build system for OCaml
  9. …before ratification, where it wasn't clear that Zbs needs to be supported. See the discussion here: https://github.com/llvm/llvm-project/pull/122164#issuecommen...
    comment by camel-cdr · 2025-01-28 · in SiFive's P550 Microarchitecture
  10. Both fantastic and 35 years too late? more refs https://github.com/llvm/llvm-project/blob/main/clang/docs/Bo...
    comment by keyle · 2025-01-24 · in The preview of -fbounds-safety is now accessible to the community
  11. …mapped file, while compressed debug symbols probably need to be extracted to anonymous memory. https://github.com/llvm/llvm-project/issues/63290
    comment by CodesInChaos · 2025-01-19 · in Rust: Investigating an Out of Memory Error
  12. …First of all, a recent LLVM patch apparently changes codegen to use CMOV instead of a branch: https://github.com/llvm/llvm-project/pull/102885 Beyond that, Intel recently updated their manual to retroactively define the behavior of BSR/BSF…
    comment by comex · 2025-01-17 · in Branchless UTF-8 Encoding
  13. …manner without a hardware instruction using a conditional move and a de Bruijn sequence; see https://github.com/llvm/llvm-project/blob/main/flang/include... .
    comment by pklausler · 2025-01-17 · in Branchless UTF-8 Encoding
  14. Bolt can do quite a lot of optimizations: https://github.com/llvm/llvm-project/tree/main/bolt
    comment by pajko · 2025-01-07 · in Size Optimization Tricks (2022)
  15. …the intention of those macros is to generate uniquely named local lambda. Cleaner version is like: https://github.com/llvm/llvm-project/issues/100869#issue-243...
    comment by fuhsnn · 2025-01-07 · in C: Simple Defer, Ready to Use
  16. …warnings, which is the next best thing: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  17. …against both GCC and LLVM requesting warnings: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427 If/when they are implemented, they will become errors with -Werror.
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  18. …against both GCC and LLVM requesting warnings: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  19. …against both GCC and LLVM requesting warnings: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427 Once the compilers begin emitting warnings, this should not be an issue anymore as long…
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  20. …warnings to protect people from doing this: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  21. …against both GCC and LLVM asking for one: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  22. …a C function or to a C++ noexcept function: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427 Perhaps the C++ standards committee should specify that doing this should cause a compiler…
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  23. …against both GCC and LLVM requesting warnings: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  24. …compilers issue them and developers heed them: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  25. …against both GCC and LLVM asking for one: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  26. …that would inform developers of the risk: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118263 https://github.com/llvm/llvm-project/issues/121427
    comment by ryao · 2025-01-01 · in Debugging memory corruption: who the hell writes "2" into my stack? (2016)
  27. this is an LLVM project... you want this to work on Metal, ask apple to add a Metal backend to LLVM https://github.com/llvm/llvm-project/tree/main/llvm/lib/Targ...
    comment by almostgotcaught · 2024-12-14 · in Using Libc for GPUs
  28. …can generate non-temporal ops if you ask for it explicitly in some form. And they are problematic: https://github.com/llvm/llvm-project/issues/64521
    comment by dzaima · 2024-12-13 · in Programming Language Memory Models (2021)
  29. …that has already been through PGO/FDO. ...assuming your workload matches the profiled workload. see https://github.com/llvm/llvm-project/blob/main/bolt/docs/Opt...
    comment by canucker2016 · 2024-11-19 · in Ubuntu Praises 5~7% PGO Compiler Optimization Performance Benefits
  30. …allocated to the operator new implementation. If you want to experiment here’s the implementation: https://github.com/llvm/llvm-project/pull/113510
    comment by olliej · 2024-11-15 · in Speculations on arenas and custom strings in C++
  31. …to implement it competitively. Is that actually what's happening? From the discussion you link ( https://github.com/llvm/llvm-project/pull/104574 ), it seems like the X280 behavior is currently still widespread. Do we know when the…
    comment by janwas · 2024-11-09 · in RISC-V Vector Extension for Integer Workloads: An Informal Gap Analysis
  32. …back in early 2022, thus closing a feature request that had been open for 11 years at the time: https://github.com/llvm/llvm-project/commit/79d08e398c17e83b... I think the other two major vendors had already switched by then, although I'm…
    comment by quuxplusone · 2024-08-30 · in Calendar Queues: A Fast O(1) Priority Queue Implementation (1988)
  33. …all over kilobytes of machine code. For comparison, see the x86 implementations in LLVM libc. https://github.com/llvm/llvm-project/blob/main/libc/src/stri...
    comment by jeffbee · 2024-08-26 · in Linux Pipes Are Slow
  34. …preserve_none was incompatible with the sanitizers, but I believe this may have been fixed by: https://github.com/llvm/llvm-project/pull/81048
    comment by haberman · 2024-08-19 · in Parsing protobuf at 2+GB/s: how I learned to love tail calls in C (2021)
  35. …from the previous stack frame after a tail call, and that would include Gerben's first example in https://github.com/llvm/llvm-project/issues/72555 Your slimcc project looks really interesting, thanks for the pointer.
    comment by haberman · 2024-08-19 · in Parsing protobuf at 2+GB/s: how I learned to love tail calls in C (2021)
  36. …and argument stack don't exceed what's provided. Debug/profiling side might hate it, though. [0] https://github.com/llvm/llvm-project/issues/72555 [1] https://github.com/fuhsnn/slimcc/
    comment by fuhsnn · 2024-08-19 · in Parsing protobuf at 2+GB/s: how I learned to love tail calls in C (2021)
  37. …that will make preserve_none allocate arguments in the registers that are usually callee-saved: https://github.com/llvm/llvm-project/pull/88333 This will make [[musttail]] + preserve_none a winning combination when used together,…
    comment by haberman · 2024-08-19 · in Parsing protobuf at 2+GB/s: how I learned to love tail calls in C (2021)
  38. …since some architectures will allow tail calls even for functions that do not perfectly match: https://github.com/llvm/llvm-project/issues/54964 "But then the code would be nonportable." True, but tail call optimization is inherently…
    comment by haberman · 2024-08-19 · in Parsing protobuf at 2+GB/s: how I learned to love tail calls in C (2021)
  39. …://gcc.gnu.org/bugzilla/show_bug.cgi?id=55522 Early 2023: bug is fixed. Feb 2024: clang follows suit: https://github.com/llvm/llvm-project/pull/80475 And maybe later this year this problem will finally be gone in common Linux distros.
    comment by amluto · 2024-08-11 · in Someone's been messing with Python's floating point subnormals
  40. I am being silenced for speaking the truth! https://github.com/llvm/llvm-project/commit/12728e144994efe8... https://clang.llvm.org/docs/LanguageExtensions.html#c11-gene...
    comment by Conscat · 2024-08-05 · in Improving _Generic in C2y
  41. …And the reason why I got so many "./" was due to a clang preprocessor bug that modifies __FILE__: https://github.com/llvm/llvm-project/issues/43825
    comment by omoikane · 2024-07-31 · in `find` + `mkdir` is Turing complete
  42. …assembler patch that will eliminate almost all mapping symbols without breaking disassemblers https://github.com/llvm/llvm-project/pull/99718 - RISC-V ISA extension `$x<ISA>` (unimplemented yet) would raise question where the relocatable…
    comment by MaskRay · 2024-07-22 · in Mapping Symbols: Rethinking for Efficiency
  43. …indices that each select a separate register, and blend those shuffled together all in one uop. https://github.com/llvm/llvm-project/issues/79196 also mentions this in "we want the elements to come from as few DLENs of the source vector as…
    comment by dzaima · 2024-07-21 · in Linus Torvalds says RISC-V will make the same mistakes as Arm and x86
  44. …bisecting functions when given assembly produced by working baseline and “bad” compiler to compare: https://github.com/llvm/llvm-project/blob/main/llvm/utils/ab...
    comment by MatzeBraun · 2024-07-19 · in Hash-based bisect debugging in compilers and runtimes
  45. Ok, 18.1.8 uploaded [1] [2]. [1] https://github.com/llvm/llvm-project/releases/tag/llvmorg-18... [2] https://discourse.llvm.org/t/18-1-8-has-been-tagged/79726/10...
    comment by quic_bcain · 2024-07-06 · in Integrated assembler improvements in LLVM 19
  46. This looks like iffy blogspam of https://github.com/llvm/llvm-project/blob/main/bolt/docs/Opt... The claim in it is 'up to 5% improvement' so the title seems overstated as well.
    comment by pvg · 2024-07-03 · in Meta Sees ~5% Performance Gains to Optimizing the Linux Kernel with Bolt
  47. …knows where else there might be pre-builts? There used to be something just like that for v17, like https://github.com/llvm/llvm-project/releases/download/llvmo...
    comment by Keyframe · 2024-07-01 · in Integrated assembler improvements in LLVM 19
  48. …planned: - Removing per-instruction timers, which add a measurable overhead even when disabled ( https://github.com/llvm/llvm-project/pull/97046 ) - Splitting AsmPrinterHandler (used for unwind info) and DebugHandler (used also for…
    comment by aengelke · 2024-07-01 · in Integrated assembler improvements in LLVM 19
  49. …However, due to complex interactions in the backend, this does not actually happen in this case ( https://github.com/llvm/llvm-project/issues/94829 ).
    comment by nikic · 2024-06-09 · in Compilers are too smart
  50. …the output back to an object file. The test cases are a good way to explore the functionality: https://github.com/llvm/llvm-project/tree/main/llvm/test/too... https://github.com/llvm/llvm-project/tree/main/llvm/test/too...
    comment by MaskRay · 2024-05-28 · in Evolution of the ELF object file format