frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

We Removed Ollama from Return

https://returneditor.ai/blog/not-a-setting-why-we-removed-ollama/
1•michall9k•37s ago•0 comments

The Business Model That Depends on You Not Bothering

https://maxvotek.com/p/the-business-model-that-depends-on
1•sbulaev•1m ago•0 comments

Why compute and general search will always beat human cleverness in AI (2019)

http://www.incompleteideas.net/IncIdeas/BitterLesson.html
1•utiiiD•1m ago•0 comments

Claude Isn't Allowed to Write Me Prose

https://blog.kvit.app/posts/agent-not-allowed-to-write-prose/
1•skolos•2m ago•0 comments

Neal Stephenson responds with wit and humor

https://slashdot.org/story/04/10/20/1518217/neal-stephenson-responds-with-wit-and-humor
1•jdkee•3m ago•0 comments

QueryAST Lens – Cross-platform SQL workbench with AST visualizer

https://github.com/Hemlig371/queryast-lens
1•Hemlig371•3m ago•0 comments

Campfire Rewritten in Rust By DHH

https://twitter.com/dhh/status/2104633108092092880
1•zac23or•5m ago•0 comments

Nvidia launches record $150B share buyback

https://www.ft.com/content/88e87863-4cf6-4c4e-8858-f0099db350d4
1•specproc•5m ago•0 comments

AirPunk – we turned starting an online business into a game

https://airpunk.ai/
1•laurenz-bauer•6m ago•0 comments

Evan Doorbell's Phone Tapes

https://evan-doorbell.com/
1•cl3misch•6m ago•0 comments

Why Tokyo transit gates process contactless cards in under 100ms

https://atadistance.net/2019/08/13/transit-gate-evolution-do-qr-codes-suck-for-transit/
1•utiiiD•6m ago•0 comments

Zenni ID Guard: Helps Disrupt Unwanted Tracking and Defend Your Privacy

https://www.zennioptical.com/id-guard
1•embedding-shape•6m ago•0 comments

Using the SNES Super FX Chip to Run Super Mario 64

https://hackaday.com/2026/09/28/using-the-snes-super-fx-chip-to-run-super-mario-64/
1•metrofun•7m ago•0 comments

Facebook Lost the Trust of Its Eyes

1•josseppi•8m ago•0 comments

I made Boonful, you can build with your assistant, sell it, and schedule.

https://boonful.io/
1•atifhub•8m ago•1 comments

MicroLLM Lab – Try 7 tiny LLM's in the browser

https://stateofutopia.com/experiments/microllmlab/
2•logicallee•11m ago•1 comments

Let's See Paul Allen's SIMD CSV Parser

http://chunkofcoal.com/posts/simd-csv/
2•hellerve•11m ago•0 comments

Stephan Wolfram on the Future for Math Research in the Age of AI

https://writings.stephenwolfram.com/2026/09/whats-the-future-for-pure-math-research-in-the-age-of...
2•alok-g•11m ago•0 comments

Vinext 1.0 Vite-powered NextJS Apps

https://blog.cloudflare.com/vinext-nextjs-on-vite/
2•matthova•12m ago•1 comments

Burning Man Death Rates – A Short Lesson in Statistics

https://ihavenapkinthoughts.substack.com/p/burning-man-death-rates-a-short-lesson
2•viraj_shah•12m ago•0 comments

Deeper Diving into early 20th century diving gear

https://www.divescrap.com/DiveScrap_INDEX/INDEX_USA.html
2•sans_souse•15m ago•1 comments

Windows 10 breaks less often than Windows 11

https://www.osnews.com/story/146039/windows-10-breaks-far-less-often-than-windows-11/
2•speckx•15m ago•0 comments

Can AI Control a Spacecraft?

https://substack.com/@thejeevankumar/note/c-348060494
2•lroe•16m ago•0 comments

Claude Sonnet 5.5 (Max Effort) Intelligence, Performance and Price Analysis

https://artificialanalysis.ai/models/claude-sonnet-5-5
3•Topfi•17m ago•0 comments

Show HN: iCli – Postgres health reporter and index optimizer

https://github.com/abhiraj-ku/iCli
2•abhirajabhi312•18m ago•0 comments

Sonnet 5.5 trumps Fable 5.1 on Artificial Analysis

https://artificialanalysis.ai
3•ghoshbishakh•18m ago•0 comments

The Making of Prince of Persia: Notes on a four-year project

https://domelian.substack.com/p/read-this-before-your-next-long-project
1•domelian•20m ago•0 comments

Sandbox Provider Costs

https://sandbox-monthly-costs.mert-569.workers.dev/
1•warthog•21m ago•0 comments

Show HN: Remria – A Cloud Computer OS

https://remria.com/
1•tshepom•21m ago•0 comments

Show HN: Semloop – Semantic loop detection for AI agent traces

https://github.com/VBS2004/semloop
1•VBS2004•24m ago•0 comments
Open in hackernews

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

https://github.com/evelance/brainiac
5•0x000xca0xfe•1y 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•1y 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•1y 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•1y 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.