frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

What Is ChatGPT Doing?

https://www.vibediary.dev/essays/chatGPT
1•stopachka•5m ago•0 comments

Microarchitecture: What Happens Beneath [video]

https://www.youtube.com/watch?v=BVVNtG5dgks
1•subset•12m ago•0 comments

How North Korea Hid an IT Workforce Inside US Companies [video]

https://www.youtube.com/watch?v=-gjnrMg9iSo
2•stevenjgarner•23m ago•0 comments

AI Withholds Life-or-Death Information Unless You Know the Magic Words

https://substack.com/home/post/p-182524207
1•llamataboot•24m ago•0 comments

Ask HN: At 34, can I aspire to being more than a JavaScript widget engineer?

3•yesitcan•24m ago•0 comments

Is Time Ripe to Throw Your Engineers Under the Trolley

https://medium.com/@farhanhubble/is-time-ripe-to-throw-your-engineers-under-the-trolley-f8d2306d24ae
2•farhanhubble•25m ago•0 comments

Ask HN: Does open-sourcing in B2C usually cripple monetization prospects?

2•schelskedevco•28m ago•0 comments

Ruby 4.0.0 Released

https://www.ruby-lang.org/en/news/2025/12/25/ruby-4-0-0-released/
4•FBISurveillance•30m ago•0 comments

Newtype Index Pattern in Zig

https://matklad.github.io/2025/12/23/zig-newtype-index-pattern.html
1•emschwartz•31m ago•0 comments

The Future of Veritasium

https://www.youtube.com/watch?v=piHGnG4LsmQ
2•rochansinha•31m ago•0 comments

Children's Holiday Letters to Satan

https://www.newyorker.com/humor/daily-shouts/childrens-holiday-letters-satan
2•smurda•34m ago•0 comments

US Software Engineer Compensation Trends: Continued Growth (2024–2025)

https://devnavigator.com/2025/12/24/us-software-engineer-compensation/
3•zuhayeer•39m ago•1 comments

Querying 160 GB of Parquet Files with DuckDB in 15 Minutes

https://datamethods.substack.com/p/querying-160-gb-of-parquet-files
1•zekrom•45m ago•0 comments

The LPU (Language Processing Unit)

https://groq.com/lpu-architecture
2•peter_d_sherman•46m ago•1 comments

The battle to stop clever people betting

https://www.economist.com/christmas-specials/2025/12/18/the-battle-to-stop-clever-people-betting
3•rmason•53m ago•2 comments

The 'Exciting Business Opportunity' That Ruined Our Lives

https://www.theatlantic.com/ideas/archive/2025/01/amway-america/681479/
2•sgerenser•53m ago•0 comments

Trending Terminals

https://itrending.top/terminal/
1•handfuloflight•54m ago•0 comments

Winnie-the-Pooh brings 100 years of fame to forest

https://www.bbc.com/news/articles/c4g9dzj1xj3o
2•1659447091•54m ago•0 comments

The subtle Red of HN and so minimalist and beautiful

2•kinj28•55m ago•1 comments

Oxaide: Sovereign AI knowledge engine for private infrastructure

https://oxaide.com
1•leewenjie•56m ago•0 comments

Load and store forwarding in the Toy Optimizer

https://bernsteinbear.com/blog/toy-load-store/
1•todsacerdoti•1h ago•0 comments

The Future of Fixing Technology (By Denver Gingerich at Fossy 2025) [video]

https://www.youtube.com/watch?v=YiKAlrGM06c
1•pabs3•1h ago•0 comments

The universe may be lopsided

https://theconversation.com/the-universe-may-be-lopsided-new-research-265256
3•aburan28•1h ago•1 comments

Python Applied Mathematics Labs

https://labs.acme.byu.edu/Pages/intro.html
28•vvin•1h ago•2 comments

No Longer Evil – new life for dead/outdated Nest Generation 1 and 2 thermostats

https://nolongerevil.com/
1•pabs3•1h ago•1 comments

Login Issues Impacting Fortnite, Rocket League, Fall Guys

https://status.epicgames.com
2•ryanhn•1h ago•1 comments

Microsoft denies rewriting Windows 11 in Rust using AI

https://www.windowslatest.com/2025/12/24/microsoft-denies-rewriting-windows-11-using-ai-after-an-...
6•zdw•1h ago•1 comments

We Saved Reboot [video]

https://www.youtube.com/watch?v=L00jx-GH2w8
1•jonny_eh•1h ago•0 comments

Understanding AI Benchmarks

https://blog.sshh.io/p/understanding-ai-benchmarks
1•gmays•1h ago•0 comments

.NET R&D Digest (December 2025)

https://olegkarasik.wordpress.com/2025/12/24/net-rd-digest-december-2025/
2•azhenley•1h ago•0 comments
Open in hackernews

Show HN: Brainfuck to RISC-V JIT compiler written in Zig

https://github.com/evelance/brainiac
5•0x000xca0xfe•7mo ago
Hi everybody,

this was my project to learn Zig and RISC-V+x86_64 assembly.

Not sure if anybody is actually interested in yet another Brainfuck compiler, so I'll just write up some random things I learned while building it!

- A primitive assembly stitching compiler is 10x faster than the interpreter. Did not expect that.

- The generated x86 code is really bad (e.g. it always uses 6 or 7 byte sized instructions with 32-bit immediates when there are much smaller ones) but it doesn't really matter. Good code generated by GCC and clang for transpiled Brainfuck->C is not much faster as it's bottlenecked by memory accesses anyways.

- Zig is pretty far along actually. You can make serious projects with it!

- But the community seems to like self-punishment. Unused parameters and variables are hard errors and there is no way to disable that even for debug builds. Makes quickly commenting out part of the code a real PITA.

- I've had a miscompilation due to std.mem.span being broken and two source code breaks going from Zig 0.13 to 0.15 (std.mem.page_size got removed and ArrayList.popOrNull as well).

- But arbitrary size integers are fantastic! And well-defined two's complement behaviour!

Here is for example the code that encodes the c.beqz instruction:

  /// Branch if Equal to Zero (compressed): c.beqz rs1', offset -> beq rs1, x0, offset
  pub fn c_beqz(text: *std.ArrayList(u8), rs1: RV_X, offset: i9) !void {
      std.debug.assert(is3BitReg(rs1));
      std.debug.assert(@mod(offset, 2) == 0);
      const imm: u9 = @bitCast(offset);
      const RV_CB = packed struct(u16) {
          op: u2,
          offset5: u1,
          offset1_2: u2,
          offset6_7: u2,
          rsd_rs1_: u3,
          offset3_4: u2,
          offset8: u1,
          funct3: u3,
      };
      const ins = RV_CB {
          .op = 0x1,
          .offset5 = @truncate(imm >> 5),
          .offset1_2 = @truncate(imm >> 1),
          .offset6_7 = @truncate(imm >> 6),
          .rsd_rs1_ = @truncate(@intFromEnum(rs1) - 8),
          .offset3_4 = @truncate(imm >> 3),
          .offset8 = @truncate(imm >> 8),
          .funct3 = 0x6,
      };
      try appendInstruction(text, u16, @bitCast(ins));
  }
This is really nice as all the exotic integer sizes are actually checked, too.

- Zig support for Windows is good. Porting the project to Windows was very easy.

- When the RISC-V registers are carefully chosen, almost all instructions could be compressed in this projects.

- Compressed instructions and good branching code (using the branch instructions directly when the jump range is small enough instead of branching over a larger jump instruction) did not noticeably change performance on real hardware (OrangePi RV2).

- But somehow QEMU got a massive boost from that. Not sure why exactly.

So, that's about it!

I hope at least something was interesting...

Comments

sylware•7mo ago
thumbs up for this project (everything RISC-V is usually).

I write rv64 assembly (nearly core only, without memory reservation instructions) and run it on x86_64 with a very small (x86_64 assembly written) interpreter.

And your are right, I have had thoughts about a "RISC-V" x86_64 compiler (but it will probably require some runtime unfortunately).

Hopefully, rv22+ hardware with ultra-performant µ-architecture and with the latest silicon process will happen sooner than we expect. One less PI toxic lock and cleaner, _really standard_ assembly (the end game of much software).

0x000xca0xfe•7mo ago
Yeah I can't wait for a performant RISC-V core. Runtime code generation is so easy for RISC-V. I have many ideas or projects where I'd like to use it but it feels kinda pointless when JITed RISC-V machine code on current hardware gets destroyed by any half-decent x86 PC or Mac running naive C code.
sylware•7mo ago
Well, here are the tricks: interpreted rv64 assembly will be "slow"... actually "slower" than x86_64 native code... but in many execution contexts, for many pieces of software, here the first trick: the "slow" interpreted rv64 assembly machine code will be... "fast" enough... The 2nd trick: I have control on my rv64 machine interpreter, and I can write native x86_64 acceleration assembly along side of a rv64 reference implementation (I planned to do just that for my CPU renderer in my wayland compositor... actually I have already AVX2 code for some of that, even though the sweet spot is AVX512, but don't have the hardware for this, yet).

And once we have this rv64 shiny hardware, certainly won't be a drop-in, but the distance to code will be minimal.

One important SDK thing: I am careful at using the smallest number of rv64 machine instructions (we tend to forget 'R' in "RISC-V" means 'R'educed...), and I use basic, really basic, C preprocessors instead of the assembler preprocessor in order to decouple the assembly code from a specific assembler preprocessor. I don't even use assembler pseudo-instructions, or ABI register names, neither compressed machine instructions.

On top of that: I don't use ELF, I use a super minimal executable/system interface dynamic shared library format of my own, omega idiotically simple, which I wrap in ELF binaries for transparent support. People have to come to realize, ELF complexity, for a executable/system interface dynamic shared library is utterly and completely obsolete, even a liability once you are looking for binary stability in time (cf games), proven over more than the last decade.