frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: MM to Inches converter with fractional inch references

https://mm-to-inches.net
1•robot1996•1m ago•0 comments

Concentration of power in AI is a risk, by Andy Konwinski

https://xcancel.com/i/article/2072830533739192560
1•alecco•1m ago•0 comments

The "Collosophone"

https://pressforsound.com/tag/collosophone/
1•Eridanus2•3m ago•0 comments

AWS Lambda MicroVMs: The Compute Nobody Asked For?

https://www.confessionsofadataguy.com/aws-lambda-microvms-the-compute-nobody-asked-for/
1•nosky•4m ago•0 comments

8 Comprehensive WebSite Health Check Ups

https://urlwatch.io/
1•mssblogs•8m ago•0 comments

Claude Design System Prompt

https://github.com/Trystan-SA/claude-design-system-prompt
1•handfuloflight•13m ago•0 comments

Creed: Canonical Markdown File

https://creed.md/home
1•handfuloflight•16m ago•0 comments

Train SIM Created by Just One Person Is Being Called the Best Ever Made

https://kotaku.com/a-train-sim-created-by-just-one-person-is-being-called-the-best-ever-made-2000...
2•oumua_don17•17m ago•0 comments

Apocketlypse

https://0dd.company/galleries/triumph/1.html
5•scaglio•25m ago•0 comments

Surus Agentic Postgres Companion

https://github.com/Geometrein/surus
1•geometrein•25m ago•1 comments

Show HN: Super fast pipeline for finding specific paths across mills of domains

https://github.com/Kirill89/webcensus
1•k1r111•29m ago•0 comments

A Postmortem of an LLM Social Network

https://armx64.medium.com/emergence-without-understanding-a-postmortem-of-an-llm-social-network-9...
1•_pdp_•34m ago•0 comments

Show HN: Reactive Resume v5 – free, private, self-hostable resume builder

https://github.com/amruthpillai/reactive-resume
1•AmruthPillai•36m ago•0 comments

Arrest 0.2.1, an HTTP client with data validation

https://github.com/s-bose/arrest
1•s-bose•37m ago•1 comments

Letter addressed to 'woman in Cornwall shed' arrives at its correct home (2021)

https://metro.co.uk/2021/07/01/letter-addressed-to-woman-in-cornwall-shed-arrives-at-its-correct-...
1•joebig•38m ago•0 comments

Bad Epoll (CVE-2026-46242)

https://github.com/J-jaeyoung/bad-epoll
1•g0xA52A2A•41m ago•0 comments

A Theory of Arrays (ToA) Union Find

https://www.philipzucker.com/toa_unionfind/
1•g0xA52A2A•55m ago•0 comments

Web-based cryptography is always snake oil

https://www.devever.net/~hl/webcrypto
1•enz•56m ago•0 comments

Knowledge Should Not Be Gated

https://www.formaly.io/blog/knowledge-should-not-be-gated
1•nezhar•57m ago•0 comments

India seeks to quell public backlash on ethanol-mixed fuel

https://www.reuters.com/world/india/india-seeks-quell-public-backlash-ethanol-mixed-fuel-after-ex...
1•JumpCrisscross•1h ago•0 comments

SigMap: 97% token reduction for AI coding sessions

https://sigmap.io/
3•handfuloflight•1h ago•0 comments

Notaru

https://notaru.org/
1•handfuloflight•1h ago•0 comments

Show HN: I trained a language model that thinks the capital of Japan is Paris

https://hamiltonianresearch.xyz/blog/hr-diffuse-1.html
4•farisallafi•1h ago•0 comments

code-on-incus: Give each AI agent its own isolated machine with root

https://github.com/mensfeld/code-on-incus
1•Tomte•1h ago•0 comments

Programmers need to start meditating now

https://jacob.gold/posts/programmers-need-to-start-meditating-now/
2•enz•1h ago•0 comments

NirCmd – Windows command line tool

https://www.nirsoft.net/~nirsoft/utils/nircmd.html
1•thunderbong•1h ago•0 comments

Paul Pelosi in hit-and-run in Napa County wine country, police say

https://www.sfgate.com/news/politics/article/paul-pelosi-in-hit-and-run-in-napa-county-wine-22332...
1•turtlegrids•1h ago•0 comments

BESS deployment to escalate as lenders see the light

https://tamarindo.global/insight/analysis/bess-deployment-to-escalate-as-lenders-see-the-light/
1•zeristor•1h ago•1 comments

Fast Software, the Best Software

https://craigmod.com/essays/fast_software/
1•ustad•1h ago•0 comments

Electronic Engineers Master Catalog

https://archive.org/details/electronicengine00unse_8
1•ustad•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.