What is your favorite word size / bus width / cpu type?
I personally like 8 bit for its simplicity. I also like 64 bit because it's really fast.
I like 64 bits because it seems to run most of my programs, but I like 8 bit because it's simple. However, I would probably need to try ASM on various CPU types to really judge what is more convenient to develop on.
I never wrote software in asm for 16 bit systems. I should get one of those 16 bit PIC microcontrollers and mess around with it.
You could get a TI-80 calculator and flash the ROM chip :trollface: . IIRC it uses some proprietary 16-bit CPU from TI that TI-Planet documented once. It's 980 kilohertz, though.
Well technically you could make a 64bit cpu that's as simple as the z80. :P It's just that modern ISAs are much more evolved to fulfill modern needs.
32 bits because SuperH (and because setting up 32 bit game on a 64bit system can be a PITA sometimes)
I like 8 bits for it's small size and easy programmability for things like a calculator, but I like higher bit counts (32 and 64) for a computer which I use to do things. 64 bit has the advantage of lotsa memory, but who needs that :P
By the way, is it true that a 8 bit processor is really not suited for a language like C, to the point where it will be even slower and larger than compiled Axe Parser code in comparison?
Modern microcontrollers can be programmed in C just fine. I programmed AVR's in C. Ofc assembly can be more optimized.
Quote from: Hooloowalrus on December 11, 2014, 05:02:54 PM
I like 8 bits for it's small size and easy programmability for things like a calculator, but I like higher bit counts (32 and 64) for a computer which I use to do things. 64 bit has the advantage of lotsa memory, but who needs that :P
Hard drive users who want a responsive system. :P
Also at the C thing, it's just that 1) the z80 was made to be programmed only in asm and 2) no compiler actually tries to optimize a lot so the code is around the speed and size of the older versions of Axe. As Keoni said, AVR's and PIC's can be programmed in C perfectly fine.
Quote from: StreetquoteAlso at the C thing, it's just that 1) the z80 was made to be programmed only in asm and 2) no compiler actually tries to optimize a lot so the code is around the speed and size of the older versions of Axe. As Keoni said, AVR's and PIC's can be programmed in C perfectly fine.
I just got the reason HBE won't be done in C for TI. Thanks.
Welp, SirCmpwn is forking sdcc for KnightOS so there might be some improvements on optimization. :) Remember, the z80 was designed in the 80's when c didn't even exist. :P
Ah that's cool then. Hopefully this also makes it easier to make cross-OS programs that way too.