frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Investors temper Anthropic IPO valuation expectations over growth slowdown

https://www.reuters.com/business/finance/investors-temper-anthropic-ipo-valuation-expectations-ov...
2•xqcgrek2•1m ago•0 comments

Google's selfie video sign-in puts your face on its servers

https://proton.me/blog/google-selfie-video
4•jethronethro•9m ago•0 comments

OBSD 8

https://cdn.openbsd.org/pub/OpenBSD/8.0/ANNOUNCEMENT
1•cacilds•9m ago•0 comments

Vortex Code: one prompt, an AI software team that ships

https://spinozalabs.ai/news/introducing-vortex-code
1•Krissh_C•9m ago•0 comments

Show HN: Resourcedeck, free and open source resource and portfolio planning

https://resourcedeck.app/
1•Gshaheen•11m ago•0 comments

AI Discovery Index

https://mojodojo.io/ai-discovery-index
3•zenincognito•11m ago•1 comments

Ask HN: What Have You Built Privately with AI That You'd Like to Share?

1•erelong•13m ago•0 comments

Making DNS_Erlang Fast: Binary Tricks for the Beam

https://blog.dnsimple.com/2026/10/making-dns-erlang-fast/
1•signa11•16m ago•0 comments

Read old.reddit.com logged out, forever

3•spezmoddedjailb•17m ago•0 comments

Accused OpenAI spy had folder called "Saudi Gov Docs," FBI says

https://arstechnica.com/tech-policy/2026/10/accused-openai-spy-had-folder-called-saudi-gov-docs-f...
2•Metacelsus•22m ago•0 comments

Astronomers discover the first ever green star

https://www.space.com/astronomy/stars/astronomers-discover-the-1st-ever-green-star-a-cosmic-zombi...
1•bushwart•24m ago•1 comments

The Hugging Face Incident

https://huggingface.wtf/
1•erwald•27m ago•0 comments

Did Ente Locker copy my code without attribution?

https://fairscan.org/blog/did-ente-locker-copy-my-code-without-attribution/
2•mtlynch•27m ago•0 comments

Community Notes for Everything

https://commonnotes.net/
2•toomuchtodo•29m ago•1 comments

Tenstorrent raises $1.5B [$6.2B valuation] to expand its open compute ecosystem

https://siliconangle.com/2026/10/19/chip-legend-jim-kellers-tenstorrent-raises-1-5b-to-expand-its...
3•peter_d_sherman•29m ago•0 comments

Show HN: Omasharp: Build Omarchy apps with C# and .NET

https://github.com/luisrudge/omasharp
2•luisrudge•29m ago•0 comments

DHH goes on white supremacist rant

https://twitter.com/dhh/status/2111638580229439730
5•grandpajoey•29m ago•1 comments

People are using AI to make smart TVs, dumb TVs

https://techcrunch.com/2026/10/19/people-are-using-ai-to-make-their-smart-tvs-dumb-again/
2•privacyisntdead•31m ago•0 comments

PE Bench: Benchmark for private equity analyst work

https://getcompound.ai/blog/introducing-pe-bench
2•peterjliu•32m ago•0 comments

Game decompilation site is closing because AI has 'broken the community aspect'

https://www.videogameschronicle.com/news/one-of-the-biggest-game-decompilation-sites-is-closing-b...
2•CharlesW•33m ago•0 comments

Skymizer HTX301 – IP Licensable AI Accelerator Card with 384GB for 700B Models

https://skymizer.ai/products/htx301/
1•peter_d_sherman•35m ago•0 comments

Why Windows 11 still ships with Windows 95's memory manager hidden inside it

https://www.windowslatest.com/2026/10/19/why-windows-11-still-ships-with-windows-95s-memory-manag...
1•khalidkhair•36m ago•0 comments

Show HN: OpenFlow – AI Agent Workflow Builder

https://github.com/SeeRay11/OpenFlow
1•searay112023•38m ago•0 comments

Bullhorn takes staffing platform offline to contain cyberattack

https://www.bleepingcomputer.com/news/security/bullhorn-takes-staffing-platform-offline-to-contai...
1•toomuchtodo•39m ago•1 comments

Trump Appointees Asked a Federal Agency to Acquire a Voting Machine and Hack It

https://www.propublica.org/article/cisa-election-security-donald-trump
8•soundworlds•41m ago•0 comments

Show HN: Chai-UI – A design system to generative AI apps

https://chai-ui.com/
1•KazaNLP•44m ago•0 comments

The simple words that can expose any liar, according to a forensic linguist

https://www.sciencefocus.com/wellbeing/how-to-catch-a-liar-language
1•gmays•45m ago•1 comments

Advancing coding in low‑resource programming languages

https://openai.com/index/low-resource-programming-languages/#sqlite-fortran
1•smusamashah•47m ago•0 comments

The Remarkable Secrets of Olive Oil

https://www.midwesterndoctor.com/p/the-remarkable-secrets-of-olive-oil
1•bilsbie•48m ago•0 comments

I Accidentally Stepped Off the Algorithm

https://vilkeliskis.com/b/2026/1019.html
1•tadasv•48m 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.