frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The Controversial Linear No-Threshold Model

https://jnm.snmjournals.org/content/58/1/7
1•leonidasrup•1m ago•0 comments

Amazon says cloud infrastructure in Bahrain, UAE 'beyond saving'

https://thecradle.co/articles-id/39961
1•slowin•2m ago•0 comments

Housekeeping and Manpower Outsourcing Services

1•tasmiyai•3m ago•0 comments

My HP EliteDesk 800 G1 Decrypts Bitlocker

https://postimg.cc/0rj2vW64
1•sehw•4m ago•1 comments

We don't need AI regulation – leave safety to us, Nvidia's Jensen Huang says

https://techcrunch.com/2026/09/15/we-dont-need-ai-regulation-leave-safety-to-us-nvidias-jensen-hu...
2•girish_r•10m ago•1 comments

The Customizable Select

https://utilitybend.com/blog/the-customizable-select-part-one-history-trickery-and-styling-the-se...
1•nesk_•14m ago•0 comments

Schadenfreude

https://en.wikipedia.org/wiki/Schadenfreude
1•vismit2000•19m ago•0 comments

The Unwilding of Patagonia's Pollinators

https://biographic.com/the-unwilding-of-patagonias-pollinators/
1•Tomte•20m ago•0 comments

Ask HN: Are requests/demands coming from AI companies for regulation genuine?

2•atakan_gurkan•21m ago•2 comments

Show HN: MinMAX Sort – A Stable Bidirectional Selection Sort Family Algorithm

2•jodenghog•38m ago•1 comments

Prefill a 284B model on Nvidia. Decode it on Apple Silicon. Over plain 10GbE

https://github.com/chadhurley25075-png/pd-bridge
2•jnaina•39m ago•1 comments

MartyPC – A Cycle-Accurate IBM PC/XT Emulator

https://github.com/dbalsom/martypc
2•yitchelle•40m ago•0 comments

We are all Product Engineers now

https://seldo.com/posts/we-are-all-product-engineers-now/
2•ColinEberhardt•43m ago•0 comments

Show HN: An open-source Socratic coach for competitive programming

https://chromewebstore.google.com/detail/socratic-algo-coach/inppdfdpenccjiggnlfaomfnckadoaoi
1•boriskurikhin•45m ago•1 comments

Looking back on Servo's first donation-funded role

https://servo.org/blog/2026/09/15/one-year-of-sponsorship/
2•luu•45m ago•0 comments

Show HN: Check an NPM package or MCP server for malicious code before install

https://bouncer.run/check
1•nader•46m ago•0 comments

The first ever API built for dictation;Today we're launching the Dictation API

https://www.assemblyai.com/dashboard/login
1•iharnoor•47m ago•1 comments

There are no optical corrections in the Parthenon

https://doi.org/10.1098/rsos.260999
2•yzydserd•47m ago•0 comments

I wrote a kill number before I wrote the landing page copy

https://deskthaw.com/blog/preorder-mechanics/
2•aaaan•49m ago•1 comments

A software thing I built: GPS on a 25MHz 486-SX

https://forum.vcfed.org/index.php?threads/a-software-thing-i-built-gps-on-a-25mhz-486-sx.1258966/
3•JPLeRouzic•53m ago•1 comments

I built dual cam app because I had credits left and didn't know what else to do

https://play.google.com/store/apps/details?id=app.heynomad.camera.dualshot.creator.ai&hl=en
1•yugendhar•53m ago•1 comments

Noise-Coded Illumination for Forensic and Photometric Video Analysis

https://arxiv.org/abs/2507.23002
1•1e1a•54m ago•0 comments

Show HN: HTMLCATS – Editor-First Learning for HTML, CSS, and JavaScript

https://htmlcats.com/
1•chriskkim•56m ago•0 comments

Fusion in Devin Desktop and CLI

https://cognition.com/blog/local-fusion
1•ludovicianul•57m ago•0 comments

Show HN: Makerpa.ge – project hub and syncing badge across your sites

https://makerpa.ge
1•leon2589•57m ago•0 comments

IOS27 removes feature to hide safari, why?

1•robglick•58m ago•0 comments

Is Jev That Good?

https://twitter.com/completeskeptic/status/2099925682726002904
2•bchelli•58m ago•0 comments

Dan Selsam's Personal Statement on AI Risk

https://www.reddit.com/r/singularity/comments/1wgibs1/ai_2027_author_daniel_kokotajlo_tweets_mess...
1•dwaltrip•59m ago•0 comments

Where Prediction Markets Struggle

https://economist.com/graphic-detail/2026/09/10/where-prediction-markets-struggle
1•andsoitis•1h ago•0 comments

The AI Language We Can't Read: Neuralese [video]

https://www.youtube.com/watch?v=iuHddnIzKRA
1•__vivek•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•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.