HNHacker News
TopNewBestAskShowJobs

Taniwha

7,647 karma · joined November 25, 2013

submissionscomments
Taniwha··on The time the x86 emulator team found code so bad they fixed it during emulation
Yes, they were bugs, I think programmers (and their marketing people) were more focused on new features than performance
Taniwha··on The time the x86 emulator team found code so bad they fixed it during emulation
Well all they needed to do was erase the screen with white and draw on it, but their app's internal logic meant that they erased it more than once.

I was capturing QuickDraw library calls - the low level graphics primitives, to figure out where the graphics time in apps was going and found out sometimes excel did it 9 times

Of course users didn't see it more than once, but our hardware made all that wasted time run faster

Taniwha··on The time the x86 emulator team found code so bad they fixed it during emulation
I was probably not the first to have to do that, we knew what apps our customers used, making them better was the whole point of the operation

I did the architectural design for the SuperMac cards. I figured out what needed to be accelerated, dropping code into people's machines to see where the cycles were going. Others did the physical design for the first 2 cards, I did the design of the chip in the Thunder and later cards (designed the data paths and state machines and a full simulation, someone else actually laid the gates)

If your card has a SQD01 on it it's my work. It peaks at 1.5Gb/s on solid fills

Taniwha··on The time the x86 emulator team found code so bad they fixed it during emulation
To be fair this was Excell 25 years ago, may no longer be true.

One of the other bugs (the Quark/ATM one) was also because of the programmers were worried about writing over stuff that hadn't been completely erased, the Quark guys wrote a string with 2 spaces at the end through a box that masked the end of the string, the ATM font renderer saw it couldn't fit the text so it split it in half and tried again so it drew N/2 N/4 N/8 ... strings. It spent all it's time in the 68k's multiply instructions figuring out how wide the strings (and substrings) were, our fancy 24-bit character rendering hardware was an afterthought

Taniwha··on The time the x86 emulator team found code so bad they fixed it during emulation
I used to be a graphics card/chip architect for macs in the early/mid 90s - our chips were the fastest, but some programs were resistant because they did stupid stuff: pagemaker invalidated the font cache every time it went thru its main loop, quark with ATM did an n*2 thing every time it wrote text etc etc. We had special hardware to accelerate text drawing and it did nothing because the software pissed it away. We considered creating a plugin that fixed all these things, it would have been hard to maintain, in the end we travelled around to the people who made these apps and talked them through their problems

To be fair excel would erase places white that it wanted to write up to 9 times before it drew any black pixels, we made that very fast! we didn't tell them :-)

At the time 24-bit framebuffers were so slow that before we built graphics acceleration hardware people would switch back to 8-bit to get stuff done, making 24-bit/true colour your daily driver was a big step forward.

Taniwha··on AI agent bankrupted their operator while trying to scan DN42
Yup, they really wanted to hunt down that guy, he was involved with all the anti-scientology mailing lists
Taniwha··on AI agent bankrupted their operator while trying to scan DN42
There is also the true story from the first Scientology vs. Internet clash, someone trolled them that their files were being hosted on 127.0.0.1, under a court ordered deposition they tried to find out who was running this server with their secret files (because yes, they'd looked, and they were there)
Taniwha··on What is the purpose of the lost+found folder in Linux and Unix? (2014)
(My guess is that it dates from the introduction of fsck which from memory was V7 or later)
Taniwha··on What is the purpose of the lost+found folder in Linux and Unix? (2014)
I used to port Unix for a living (V6 thru SysVr3) I know it was in Vr2, and I have a man page that says "(last mod. 1/15/87)" which would likely make it SysVr1 or earlier
Taniwha··on What is the purpose of the lost+found folder in Linux and Unix? (2014)
From memory mklost+found did exactly this
Taniwha··on Restartable Sequences
The cache coherency protocols that sit between the CPUs and DRAM always essentially "use a mutex": when a cpu wants to write it broadcasts to all the other CPUs and either gets the latest copy from whoever wrote it last and shoots down any read-only copies in other CPUs or reads it from DRAM (or converts a read only copy to be writeable)

This happens on every memory access, so the thing you want to avoid is ping ponging writeable cache lines between CPUs (especially before you have a chance to actually write it) - LL/SC instructions sit on top of these protocols and allow instructions to tell is a cache line had been "stolen" before you have a chance to write it

Taniwha··on Why is Vivado 2026.1 dropping Linux support for free tier?
When I first started doing chip design my boss paid more for tools per year than he paid me ... now days open source tool chains are leaping ahead ... I don't need a boss (or VCs) in order to design chips
Taniwha··on Why is Vivado 2026.1 dropping Linux support for free tier?
Well Gowin here I come I guess
Taniwha··on Starship V3
I'm not sure they're all that simpler, the basic plumbing probably hasn't changed much, it's just that modern fabrication tech means you can hide all the complexity inside
Taniwha··on NZ Government to Disestablish the BSA
he made fishing shows, not exactly politically contentious
Taniwha··on NZ Government to Disestablish the BSA
They investigated one too many rightwinger who supported the government
Taniwha··on San Francisco streets with confusingly similar names
I lived on Dana St in Oakland at the Berkeley border, we continually found lost and confused people - the street continued down our block and stopped, reappeared after a jog a half block away, numbers got smaller as it went south, over the border numbers got smaller as the went north and the street disappears for 3 blocks as it crosses Telegraph Ave (literally where the telegraph was installed in a straight line) diagonally - 4-5 pieces with numbers going in opposite directions.

Even wore our portion was originally in Berkeley, the border was moved 100 years or so ago so that someone could open the closest bar to the campus when Berkeley had more stringent liquor licensing

Taniwha··on Ternary Bonsai: Top Intelligence at 1.58 Bits
and so you can at 1-bit too, and the hardware will be even smaller and cheaper
Taniwha··on Focused microwaves allow 3D printers to fuse circuits onto almost anything
If you can print small enough with this technology I'm pretty sure you can make transistors - sort of 1980 era transistors, not very dense, but if you are printing bulk materials you can build in 3D rather than 2D, make interesting numbers of transistors, cpus in everything!
Taniwha··on Floating point from scratch: Hard Mode
Wearing my chip designer's hat decimal FP just means more (and slower) gates
Taniwha··on Book review: There Is No Antimemetics Division
If you like unreliable narration and rug pulls Nick Harkaway's novel 'The Gone-Away World' really takes the cake (and is brilliant)
Taniwha··on Floating point from scratch: Hard Mode
Everyone who has ever had to build a floating point unit has hated it with a passion, I've watched in done from afar, and done it myself
Taniwha··on VHDL's Crown Jewel
BTW my really big peeve about modern verilog is that it never picked up {/} as synonyms for begin/end - my experiments (20 years ago) showed that it was an easy extension, the minor syntactic ambiguities were trivally fixable
Taniwha··on VHDL's Crown Jewel
I'm a long time verilog user (30+ years, a dozen or so tapeouts), even written a couple of compilers so I'm intimate with the gory details of event scheduling.

Used to be in the early days that some people depended on how the original verilog interpreter ordered events, it was a silly thing (models would only run on one simulator, cause of lots of angst).

'<=' assignment fixed a lot of these problems, using it correctly means that you can model synchronous logic without caring about event ordering (at the cost of an extra copy and an extra event which can be mostly optimised away by a compiler).

In combination 'always @(*)' and '=', and assign give you reliable combinatorial logic.

In real world logic a lot of event ordering is non deterministic - one signal can appear before/after another depending on temperature all in all it's best not to design depending it if you possibly can, do it right and you don't care about event ordering, let your combinatorial circuits waggle around as their inputs change and catch the result in flops synchronously.

IMHO Verilog's main problems are that it: a) mixes flops and wires in a confusing way, and b) if you stay away from the synthesisable subset lets you do things that do depend on event ordering that can get you into trouble (but you need that sometimes to build test benches)

Taniwha··on Alpha Micro AM-1000E and AM-1200
yeah, that's rather a pain though and it effectively leaves one 68k frozen while the other services the page fault - it means you can't run another user process while the page is being read in (because it too might cause a page fault)
Taniwha··on Alpha Micro AM-1000E and AM-1200
68451 or a custom SUN-like (SRAM, kind of like a PDP11) MMU, there was a guy who went around Silicon Valley in the mid 80s designing SUN-like MMUs for companies, they were all different, and some were broken (couldn't protect user space from kernel space).

68000s however had a problem: they couldn't return correctly from a page (MMU) fault (68010s fixed that) for a pre-VM (pre BSD or SVR2) UNIX world - however you could get around this with a few smarts

Taniwha··on Write up of my homebrew CPU build
Of course while you're doing the next version you should knock out a tiny tapeout version, it should easily fit in a single cell (maybe 2 if you want to push the 256 byte sram in as well)
Taniwha··on Chiplets Get Physical: The Days of Mix-and-Match Silicon Draw Nigh
I think that what we're all waiting for for this to take off is one of the Cheap Chinese assembly houses to set up a web site where you can drag and drop chiplets into a carrier with standard interface buses, you press a button and brrr-zap robots pull chiplet die onto a substrate, bond out the interfaces and ship you a prototype same day - because you all know this is totally the future
Taniwha··on The Singularity will occur on a Tuesday
I was at an alternative type computer unconference and someone has organised a talk about the singularity, it was in a secondary school classroom and as evening fell in a room full of geeks no one could figure out how to turn on the lights .... we concluded that the singularity probably wasn't going to happen
Taniwha··on A few CPU hardware bugs
I think FP needs it's own custom tests (billions of them!) - I hate building FP units, they are really the pits
← PreviousPage 3 of 34Next →