frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Gramma, tortoise who lived through two world wars, dies aged 141

https://www.theguardian.com/us-news/2025/nov/25/gramma-tortoise-dies-age-141
1•lentil_soup•2m ago•0 comments

Good Enough Is Reorganizing

https://goodenough.us/blog/2025-11-25-good-enough-is-reorganizing/
2•pentagrama•7m ago•0 comments

OpenAI needs to raise at least $207B by 2030, HSBC estimates

https://www.ft.com/content/23e54a28-6f63-4533-ab96-3756d9c88bad
2•jmsflknr•7m ago•0 comments

US banks scramble to assess data theft after hackers breach financial tech firm

https://techcrunch.com/2025/11/24/us-banks-scramble-to-assess-data-theft-after-hackers-breach-fin...
3•indigodaddy•9m ago•0 comments

Unifying Wikipedia mobile and desktop domains

https://techblog.wikimedia.org/2025/11/21/unifying-mobile-and-desktop-domains/
4•todsacerdoti•11m ago•0 comments

CBS to "redraw the lines of what falls in the 40 yards of acceptable debate"

https://twitter.com/DropSiteNews/status/1993154653941362892
1•sporkxrocket•11m ago•0 comments

EU set to adopt ChatControl negotiating mandate tomorrow without discussion

https://digitalcourage.social/@echo_pbreyer/115611006935923542
4•nickslaughter02•11m ago•1 comments

Neural Architecture for Dummies

https://theahura.substack.com/p/intuitive-neural-nets-for-dummies
1•theahura•12m ago•0 comments

Show HN: A better way to handoff web bugs to AI agents

https://github.com/magentic/flowlens-mcp-server
2•mzidan101•13m ago•0 comments

Show HN: Chaos Monkey middleware for LangChain (v1) agents

https://github.com/iroy2000/langchain-chaos-middleware
1•iroy2000•13m ago•0 comments

Trump's FCC: Internet Providers Can Monitor Their Own Cybersecurity Standards

https://www.cnet.com/home/internet/internet-providers-can-monitor-their-own-cybersecurity-standar...
4•mooreds•14m ago•1 comments

Web browser status bars are nuts

https://lapcatsoftware.com/articles/2025/11/4.html
1•HotGarbage•15m ago•0 comments

Show HN: Deriving General Relativity from Finite Information (Open Source)

https://github.com/loning/the-omega
1•loning•15m ago•1 comments

MacTiler – a macOS menubar window manager I've been building

https://mactiler.com/
1•simplifunner•16m ago•1 comments

Windows Digital Signage mode hides BSoDs after 15 seconds

https://www.theregister.com/2025/11/18/windows_bsod_digital_signage_mode/
2•ohjeez•16m ago•0 comments

I built my website back end in Swift instead of Rust or Node.js

https://old.reddit.com/r/iOSProgramming/comments/1p4rkry/i_used_my_15_years_of_ios_app_development/
2•busymom0•17m ago•0 comments

Popular Git Config Options

https://jvns.ca/blog/2024/02/16/popular-git-config-options/
3•sharjeelsayed•19m ago•0 comments

Ask HN: Have you used an LLM for grief support?

2•mettakindness•20m ago•0 comments

Bill Gates Foundation's 65% Microsoft Stock Dump

https://thinkmintmedia.blogspot.com/2025/11/87-billion-question-is-gates.html
1•iamtech•20m ago•0 comments

How Loud Are Cities?

https://www.datawrapper.de/blog/how-loud-are-cities
1•speckx•21m ago•0 comments

CDC instructs researchers to end all monkey studies by year-end: Science

https://www.fiercebiotech.com/research/cdc-instructs-researchers-end-all-monkey-studies-year-end-...
2•JPLeRouzic•24m ago•0 comments

Pre-Cache: A Microarchitectural Solution to Prevent Meltdown and Spectre

https://arxiv.org/abs/2511.17726
2•bikenaga•25m ago•1 comments

Market Volatility Underscores Epic Buildup of Global Risk

https://www.nytimes.com/2025/11/25/business/economy/stocks-bitcoin-markets-risk.html
2•zerosizedweasle•26m ago•0 comments

Show HN: Idealane – Intuitive vibe coding for entrepreneurs and SMBs

https://idealane.com/
1•lluiscanadell•28m ago•0 comments

Roman fingerprints found in 2k-year-old cream (2003)

https://www.theguardian.com/uk/2003/jul/28/artsnews.london
1•gradus_ad•28m ago•0 comments

Companies overpaying on employee expenses by up to 14%

https://ffnews.com/newsarticle/paytech/companies-overpaying-on-employee-expenses-by-up-to-14/
1•onpedrof•30m ago•1 comments

The Wanderer

https://randsinrepose.com/archives/the-wanderer/
1•mooreds•31m ago•0 comments

Tips on being a kinder neighbor and fostering a sense of community

https://text.npr.org/1060464791
2•mooreds•31m ago•0 comments

Lessons from testing three AI agents on the same complex task

https://prashamhtrivedi.in/ai-agent-comparison-claude-gemini-codex/
2•prash2488•32m ago•1 comments

The Return of the Viva

https://ednutting.com/2025/11/25/return-of-the-viva.html
1•EdNutting•32m ago•1 comments
Open in hackernews

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

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