On Sun, Jan 29, 2017 at 8:34 PM, Nick Downing <downing.nick(a)gmail.com> wrote: ​In 1978/79, there was a Z80 Z Compiler from either Teletype or Western Electric, that IIRC was based on the Ritchie compiler. Somebody that worked in the IH or Columbus labs might remember such as Phil Karn might be a good source. That said, is you want a goos starting point the best C compiler for the 8080 was the Leor Zolman's "Brain Damaged Software" C -- aka BDS C. Which he has put in the public Domain: http://www.bdsoft.com/resources/bdsc.html There is also the classic from Ron Cain, the "Small C Compiler" [ http://www.svipx.com/pcc/PCCminipages/zc9b6ec9e.html] which was updated and expanded by Jim Hendrix is also in the public domain: http://www.deturbulator.org/jim.asp ​ ​Close, but you have some of the history a little bent. I believe that the first C compiler for the 68000 was started at motorola ​by the 68K developers themselves (a little known fact -- what would become the 68K was developed on an PDP-11/7- running UNIX). As I understand from Les Crudele (who lead the 68K team), the compiler was based on the Ritchie compiler, but I do not think it as every taken very far. I do not believe a C tool chain was ever made available to their customers/UNIX community. We should ask some of the Moto guys about that. So, before the chip was released and became the 68K (when there were 10 beta sites and it was an eXperiment -- i.e. an "X-Series" chip), we had a couple them @ Tek Labs. Which were the basis for the Magnolia system that Roger Bates created. I hacked up the Ritchie compiler shortly there after (I was not aware of the Motorola work at the time), and created something that worked sans FP. The assembler & linker were written by Paul Blattner. My compiler used a 16 bit int. Sometime after the Tek work, Steve Ward's guys writing Trix hacked together a compiler, assembler and the like. If memory serves me, tjt wrote the assembler and hacked the linker and Jack Test did much of the compiler and again IIRC that was based on PCC. But, they did support FP and an "int" was 32 bits. I believe that this was the "seed" compiler for most of the UNIX workstations. It was scattered across the land as it were. I switch over to it at some point, although I don't remember if I switched it to a 16-bit int. I know we talked about it and I've forgotten how that all played out. ​Right the Masscomp and Apollo systems were the two most successful to use the Forest Basket "Fixer/Executor" model. The original Masscomp C Compiler was based on the MIT Compiler, as was Suns. Apollo (being Pr1mates, used Ratfor & Pascal as their systems languages at beginning) and did not cut C in until later. All three firms would start compiler teams. The Masscomp compiler team was direct decedent of the VMS Compiler team with many of the same players. Those stories are better told over beers. ;-)​ BTW: for the first 2-3 years, the reason why Masscomp was faster than Sun, and each were using the 10Mhz 68000 chips, was the Masscomp had a real optimizing compiler, in the same key as the DEC and DG compilers (al biet written in C from the ground up). The team was lead by Peter Darnell and had Marty Jack and a number of other infamous backend folks. Masscomp was getting 5-25% better performance than the MIT/PCC based one, so eventually Sun & Apollo (also have a bunch of ex-pat DECies, made similar investments).

I remember BDS C. We were early users of that. Amusingly I became affiliated with a company called BDS (no relation). We were an early player in the internet domains and I owned BDS.COM for a while.

On Sun, Jan 29, 2017 at 09:19:48PM -0500, Clem Cole wrote: Huh, I didn't know that. So he's the guy who came up with that design?

On Sun, 29 Jan 2017, Clem Cole wrote: Talk about brain-damaged software... BDS C is irretrievably broken, with all sorts of things missing. I used to use Hi-Tech C for CP/M, but I don't know whether they're still in business. It was a full ANSI C compiler, with function prototypes, initialisation assignments, static variables, etc. As Henry Spencer once said, to be called a C compiler it ought to at least be able to compile C... (And as I've said on many occasions, the true test of a compiler is whether it can compile itself.) -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."