Viewing profile — bonzini

0x86 and 0x87 (XCHG rm,r with byte- and word-sized operands) encode nops in the same way as 0x90, but were never redefined as prefixes. It's interesting that a lot of ALU operation…

z386 is in development right now, and isn't even finished. Do you mean between ao486 and z386?

None was. XCHG AX,AX is special because XCHG AX,reg has a one-byte encoding. You're probably confusing with: - POP CS being broken and later becoming a prefix - some opcodes being …

I am doing something similar to that C-to-Rust rewrite. Except: 1) I'm clearly saying that it's only for my own learning experience and to find ways to improve the original program…

The problem is that the original formulation was "most people" are unaware of being unskilled, but by now the name is used to mean "some group of people" is unaware of being unskil…

They write garbage if you turn off your brain. They write code as good as yours if you work together.

Yeah I never use non-interactive rebase. Even if I don't need to edit the todo list, reading it gives me a confirmation of what git will do.

But the real question is 1) whether other human lawyers would catch the error 2) in how much time 3) which of the errors introduced by AI vs. human would have bigger consequences. …

First of all I want to say it is not your fault, and also your article is clearly partly human, despite what Pangram says. The thing that I like the least is the headings and the w…

It's depressingly hard to find one that isn't. You see the title, think this might be interesting, and puke by the second paragraph.

Ah, so it is basically a single rotr(x|2, 2), nice

How does it do that? When the 64-bit pointer is actually a pointer, does it mangle it into something that is certainly not UTF-8 (e.g. changing its top byte to 0xC0, and assuming t…

Is the runtime compiled by the Fil-C compiler, or is it a single huge unsafe block? I honestly don't know the answer.

That's not supposed to happen. I would like to have more info.

Wikipedia does have a rule allowing "routine calculations" https://en.wikipedia.org/wiki/Wikipedia:No_original_research... Of course given the magnitude of the statement a bit of c…

What is the manufacturing tooling that you mention?

True, but adding the hollow tube to the bottom side greatly improved how much the bricks stuck together, compared to Kiddicraft. It's not a small change. Lego also tried other desi…

It doesn't have a carry flag either. Multiprecision integer operations absolutely suck in RISC-V, you need three operations (SLT and two adds, with an awful dependency chain too) t…

Indeed, it's hard to find a balance between what's too verbose and what's too hard. For relatively complex models it's also almost impossible to do "quality control" without actual…

AI is good at coding if there's an oracle. If the system is ancient, unreadable, untestable, that's exactly the opposite. It won't get the exact set of corner cases.

It depends on how much the code has changed, how easy it is to test old releases, how far back you need to merge the fix... "Cherry picking from the top of tree" is the most common…

I interpreted "I squashed them" as "I used git rebase -i to squash the oopses and fixes". If that's not what the user does, and rather squashes the PRs, then indeed I would be disa…

The why for a commit belongs in the message or code comments not in the history.

Nope. Perfectly curating history is indeed the opposite of squashing—you squash because you couldn't be bothered to curate your commits. Squashing is a workaround not an alternativ…