News for hackers. Stuff that matters.
Re:Why GCC 1.42 on the Tektronix 4404 – with a C compiler fr... by elektraglide on Tuesday December 17, 2024 @05:49PM (#42446289)
I didn't dive into that but yes, Tek4404 runtime seems to trash d2 and a2 so I had to cross compile with those marked as scratch registers.
Re:Why GCC 1.42 on the Tektronix 4404 – with a C compiler fr... by bcrl on Tuesday December 17, 2024 @08:54PM (#42447412)
I was referring to gcc bugs. Doing Linux kernel development 20+ years ago certain complex functions with lots of register spills would occasionally trip up gcc's register allocator on i386. Architectures with more registers and less complex constraints on how they were used would not trigger those bugs as frequently. Eventually, gcc got better and those kinds of bugs went away, but I got to spend many hours looking at the assembly gcc produced and raw Oopsen.
Re:Why GCC 1.42 on the Tektronix 4404 – with a C compiler fr... by dmitrygr on Tuesday December 17, 2024 @11:47PM (#42448188)
There is a branch of m68k GCC still alive and maintained today that supports palmos calling convention which is similar to this but not the same: d0-d2/a0-a1 are not preserved.