frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Exploring BPF LSM support on aarch64 with ftrace

https://www.exein.io/blog/exploring-bpf-lsm-support-on-aarch64-with-ftrace
1•ankitg12•58s ago•0 comments

Show HN: StreamVault

https://streamvaults.ru/
2•hannil55•1m ago•0 comments

Jscbjscbs

https://news.ycombinator.com/submit
1•cwsrider•6m ago•0 comments

Natural Born Bloggers

https://spyglass.org/om/
2•imartin2k•8m ago•0 comments

Empero-AI/Qwythos-9B-Claude-Mythos-5-1M

https://huggingface.co/empero-ai/Qwythos-9B-Claude-Mythos-5-1M
1•vednig•10m ago•0 comments

Ask HN: Have the founders of Palentir and Anduril ever read Tolkien?

1•nativeit•10m ago•0 comments

Scott Aaronson's Trevisan Award Acceptance Speech

https://scottaaronson.blog/?p=9881
1•Jun8•10m ago•0 comments

Show HN: Mentionkit – Track your brand mentions across LinkedIn, X and more

https://mentionkit.com/
1•shash7•13m ago•0 comments

3D-printed metal wristwatch with LED matrix display

https://old.reddit.com/r/Watches/comments/1ui3lvy/project_my_brother_and_i_designed_our_own/
1•huhtenberg•18m ago•0 comments

Turning Strava data and gym photos into a training recap with my coding agent

https://www.akashtandon.in/ai/2026-06-29-strava-photos-training-recap-coding-agent/
1•akashtndn•19m ago•0 comments

Show HN: AI agent for software user community support

2•Daniel-Pan•21m ago•1 comments

White working-class children failed by education system, says inquiry

https://www.bbc.co.uk/news/articles/cq51j10q601o
1•mmarian•23m ago•0 comments

Would Claude Refuse an Illegal Military Order?

https://www.theatlantic.com/national-security/2026/06/claude-anthropic-ai-warfare-orders/687581/
1•abdelhousni•24m ago•1 comments

Show HN: Nearest-neighbor, a dating app for AI agents

https://nearest-neighbor.replygirl.club/
1•replygirl•27m ago•0 comments

Israel deployed troops to Somaliland after recognition, source says

https://www.middleeasteye.net/news/israel-deployed-troops-somaliland-after-recognition-official
1•littlexsparkee•31m ago•0 comments

Squish – The fastest way to run local LLMs on Apple Silicon

https://squish.run/
2•jscohn85•31m ago•0 comments

Moving Car-Free as a Parent

https://maxmautner.com/2026/06/27/moving-as-a-parent.html
2•mslate•32m ago•0 comments

Names in the USA (1880-2025)

https://liorsinai.github.io/coding/2026/06/21/names.html
1•the_origami_fox•33m ago•0 comments

InnerRipple, on device health scoring against your own Apple Watch baseline

https://apps.apple.com/us/app/innerripple-know-your-health/id6774995186
1•stillraft•33m ago•0 comments

About Walt Disney

https://d23.com/about-walt-disney/
1•teleforce•35m ago•0 comments

Ask HN: What's one thing you wish AI did well?

1•akashwadhwani35•42m ago•2 comments

RedNote Xiaohongshu is said to ready Hong Kong IPO filing this month

https://www.bloomberg.com/news/articles/2026-06-15/xiaohongshu-is-said-to-ready-hong-kong-ipo-fil...
3•teleforce•47m ago•1 comments

AI coding agents(Claude, Cursor) ask questions, share learnings, and blueprints

https://agents.stackoverflow.com/recent
1•rushil_b_patel•48m ago•0 comments

Prompt Injection Defense

https://pypi.org/project/prompt-injection-defense/
1•rghosh8•51m ago•0 comments

You aren't ready to be your own boss until you read this

https://comuniq.xyz/post?t=1330
4•01-_-•51m ago•0 comments

85% of kids are still using social media despite ban

https://theconversation.com/85-of-kids-are-still-using-social-media-despite-ban-but-we-need-a-new...
2•01-_-•52m ago•0 comments

Trump's U-Turn on Iran Sanctions Would Unravel Decades of Curbs

https://www.bloomberg.com/news/articles/2026-06-28/trump-s-u-turn-on-iran-sanctions-would-unravel...
1•petethomas•52m ago•0 comments

Reinforcement learning towards broadly and persistently beneficial models

https://alignment.openai.com/beneficial-rl/
2•spicypete•57m ago•0 comments

Is Sunscreen the New Margarine?

https://www.outsideonline.com/health/wellness/sunscreen-sun-exposure-skin-cancer-science/
4•markgavalda•58m ago•0 comments

Show HN: WinPodX – run Windows apps on Linux, VM looks like real hardware

https://www.winpodx.org/
1•kernalix7•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.