MaskRay

10 ms·

1.
by MaskRay 21d ago
shameless plug: lld 23.x is significantly faster than 22.x! I wrote about the optimizations in https://maskray.me/blog/2026-04-12-recent-lld-elf-performanc... As a side note, parallel input file parsing and symbol res
2.
by MaskRay 2mo ago
Interesting to see that people are still spending much time on assembly languages :) I've had a lot of fun with it in recent years as well. (Shameless plug: I've written a few on LLVM integrated assembler regarding better fragmen
3.
by MaskRay 3mo ago
While we could utilize zigzag encoding (i>>31) ^ (i<<1) to convert SLEB128-encoded type/addend to use ULEB128 instead, the generate code is inferior to or on par with SLEB128 for one-byte encodings on x86, AArch64, and RISC
4.
by MaskRay 3mo ago
GetProgramPath consulting PATH is a pretty standard behavior inspired by GCC. Clang driver may find an external program from its program paths (e.g. -ccc-install-dir, the GCC installation's bin directory, -B, ) and then PATH. > Clan
5.
by MaskRay 7mo ago
git switch v6.9 The riscv build succeeded. For the x86-64 build I ran into % make O=/tmp/linux/x86 ARCH=x86_64 CC=/tmp/p/claudes-c-compiler/target/release/ccc-x86 HOSTCC=/tmp/p&#
6.
by MaskRay 7mo ago
I want to verify the claim that it builds the Linux kernel. It quickly runs into errors, but yeah, still pretty cool! make O=/tmp/linux/x86 ARCH=x86_64 CC=/tmp/p/claudes-c-compiler/target/release&#x2F
7.
by MaskRay 8mo ago
I accidentally published handling-long-branches.html . I actually removed it quickly, but Google Search already got it.... https://news.ycombinator.com/item?id=46759921 (Long branches in compilers, assemblers, and linkers),
8.
Long branches in compilers, assemblers, and linkers(maskray.me)
9 points by MaskRay 8mo ago|0 comments
9.
by MaskRay 8mo ago
Amazing! I read you article in 2012 when the link was https://homepages.cwi.nl/~tromp/maze.html I was learning Haskell and Ocaml and wrote my own article in Chinese then https://maskray.me/blog/201
10.
by MaskRay 8mo ago
I recall that google3 switched to -funsigned-char for x86-64 a long time ago.
11.
by MaskRay 8mo ago
Open source project maintenance follows a similar model, but with a different set of stakes. The "price tag" of voicing concerns is lower, yet raise them too often and you still earn a reputation as obstructionist. Meanwhile, the
12.
by MaskRay 9mo ago
We are missing tooling to partition a huge binary into a few larger shared objects. As my https://maskray.me/blog/2023-05-14-relocation-overflow-and-c... (linked by author, thanks! But I maintain lld/ELF instead o
13.
by MaskRay 9mo ago
Note, sections without the SHF_ALLOC flag, such as `.debug_*` sections, do not contribute to the relocation distance pressure. Many 10+GiB binaries (likely due to not using split DWARF) might have much smaller code+data and not even close t
14.
Remarks on SFrame(maskray.me)
3 points by MaskRay 1y ago|0 comments
15.
LLVM's AI policy vs. code of confuct vs. reality(discourse.llvm.org)
2 points by MaskRay 1y ago|0 comments
16.
by MaskRay 1y ago
Rex
17.
by MaskRay 1y ago
The compiler team has never had more than three people at any time, but both the language and its feature set are impressive. I don't know whether they got any sponsorship. Now that the two most prolific developers are primarily workin
18.
by MaskRay 1y ago
Tested programs: lz4 zstd brotli bzip3 xz lzham: The build system is not well-polished for Linux. I have forked it, fixed build errors due to stdint.h, and installed lzhamtest. IMHO the command line program lzhamte
19.
Understanding alignment – from source to object file(maskray.me)
5 points by MaskRay 1y ago|0 comments
20.
by MaskRay 1y ago
I don't follow Zig's development. https://ziglang.org/download/0.15.1/release-notes.html#Motiv... feels vague to me, and linking to a lengthy video isn't very clarifying. Still, I skimmed through i
21.
LLVM integrated assembler: Engineering better fragments(maskray.me)
4 points by MaskRay 1y ago|0 comments
22.
by MaskRay 1y ago
Thanks for sharing the insight! As I observed when I was at Google: tcmalloc wasn't a dedicated team but a project driven by server performance optimization engineers aiming to improve performance of important internal servers. Extract
23.
by MaskRay 1y ago
Build instructions In the llvm/llvm-project repository git switch origin/release/19.x cmake -GNinja -S. -B/tmp/out/custom -DLLVM_TARGETS_TO_BUILD='X86;AArch64' -DLLVM_ENABLE_PROJECTS=clang -
24.
Apple is adding Mach-O's riscv32 support to LLVM(github.com)
7 points by MaskRay 1y ago|1 comments
25.
by MaskRay 2y ago
Regarding: `cmpb $0, %fs:__tls_guard@tpoff`, the per-function-call overhead is due to dynamic initialization on first use requirement: > Block variables with static or thread(since C++11) storage duration are initialized the first time
26.
Simplifying Disassembly with LLVM Tools(maskray.me)
4 points by MaskRay 2y ago|0 comments
27.
by MaskRay 2y ago
I have placed a lot of focus on code navigation. Here is what I mentioned in my post: nmap('J', '<cmd>Telescope lsp_definitions<cr>', 'Definitions') nmap('<M-,>', '<cmd
28.
Tinkering with Neovim(maskray.me)
2 points by MaskRay 2y ago|1 comments
29.
by MaskRay 2y ago
The scheme proposed in this blog post is also called PrefixVarInt. Signed integers can be represented with either zigzag encoding or sign extension. For the most common one-byte encoding, zigzag encoding is a worse scheme. https:/&#x2
30.
by MaskRay 2y ago
Here is the glibc feature request: https://sourceware.org/bugzilla/show_bug.cgi?id=31959 ("Feature request: special static-pie capable of loading the interpreter from a relative path")

More ›