frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: 0day Rubbish – AI-Discovered CVSS 9.8 RCE Chain in Cisco CUCM

https://0day-rubbish.com/blog/cisco-cucm-rce-chain
1•wisdomtreelzz•57s ago•0 comments

Electric aircraft makes historic flight from Sweden to Finland

https://yle.fi/a/74-20235372
1•marklit•1m ago•0 comments

Testing Smart TV Tracking

https://www.rtings.com/tv/learn/research/smart-tv-tracking
1•ledoge•1m ago•0 comments

GitHub project mantainer has a lot of issues

1•Asil_real•1m ago•0 comments

Taiwan solved tax evasion in 1951 with a trick

https://twitter.com/i/status/2073991580986609904
2•Michelangelo11•3m ago•0 comments

Mews Cuts 15% of Staff, Points to AI in Broad Restructuring

https://twitter.com/LayoffAI/status/2074571918255194361
1•agilek•3m ago•0 comments

Jamboree – Multiplayer Synthesizer

https://jamboree.space
1•sandgiant•4m ago•0 comments

ZML/LLMD alpha – cross platform LLM server

https://zml.ai/posts/llmd/
1•steeve•6m ago•0 comments

Echoo – AI on the text you're typing in any Mac app, free to try, no API key

https://www.echoo.ai/
2•mike-el•12m ago•0 comments

A task tool I use flagged 4 of my team's tasks as 30x overdue

https://aura4app.com
1•abusalh•14m ago•0 comments

Show HN: Token-saviour – agent skill from benchmarking 9 token-saving tools

https://github.com/vagkaratzas/token-saviour
1•vagkaratzas•16m ago•0 comments

Scalable Untargeted Promptware Attacks via Adversarial HalluSquatting

https://sites.google.com/view/agentic-botnets/home
1•shscs911•16m ago•1 comments

How do we make coding agents write good code?

https://github.com/molvqingtai/The-Absolute-Code
1•molvqingtai•16m ago•0 comments

Claude bug report: Cross-session credential leakage

https://github.com/anthropics/claude-code/issues/72274
2•delamon•17m ago•0 comments

Flagship models are not always better

https://tej.as/blog/note-app-ai-benchmark-apple-intelligence-sucks
2•tejaskumar_•18m ago•0 comments

Earn 50% on Each Subscription

1•kwefnkwjen•18m ago•0 comments

Decoding the obfuscated bash script on a Uniqlo t-shirt

https://tris.sherliker.net/blog/obfuscated-self-evaluating-bash-script-by-cdn-akamai-being-suppli...
1•speerer•19m ago•0 comments

Apple Loses Spat with EU over App Store and iPhone Rules

https://www.bloomberg.com/news/articles/2026-07-08/apple-loses-spat-with-eu-over-app-store-and-ip...
2•vrganj•22m ago•1 comments

Rust service isn't leaking: when do glibc / jemalloc / mimalloc call munmap

https://pranitha.dev/posts/rust-and-memory-allocators/
1•fanf2•23m ago•0 comments

Most slopcode projects are abandoned and deleted within months of release

https://www.osnews.com/story/145469/most-slopcode-projects-are-abandoned-and-deleted-within-month...
2•latexr•23m ago•0 comments

Tiny386: ESP32 (slowly) running Windows 95

https://hchunhui.github.io/tiny386/esp32s3_win95.webm
2•kls0e•24m ago•1 comments

Apple interest thrusts China's CXMT into memory chip spotlight

https://www.ft.com/content/f4ac5c92-03be-4499-b16a-017a7e9ee228
1•0in•26m ago•0 comments

Geosql: A Claude/Codex skill for geospatial data

https://github.com/dekart-xyz/geosql
1•rzk•27m ago•0 comments

SQLite-utils 4.0, now with database schema migrations

https://simonwillison.net/2026/Jul/7/sqlite-utils-4/
1•pretext•30m ago•0 comments

Adiabatic Circuit

https://en.wikipedia.org/wiki/Adiabatic_circuit
1•tristenharr•34m ago•0 comments

Zero Copy

https://en.wikipedia.org/wiki/Zero-copy
2•tristenharr•35m ago•0 comments

Interview: Drew DeVault on an AI-free version of Vim

https://jasonpolak.substack.com/p/interview-drew-devault-on-an-ai-free
2•vouaobrasil•36m ago•0 comments

Files SDK

https://files-sdk.dev
2•handfuloflight•37m ago•0 comments

Windows Privilege Abuse

https://www.semperis.com/blog/windows-privilege-abuse-can-lead-to-active-directory-compromise/
1•ishqdehlvi•38m ago•0 comments

Show HN: Orchestrator – a single-binary workflow orchestration tool

https://github.com/webstonehq/orchestrator
1•mikenikles•39m ago•1 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.