SDCC – Small Device C Compiler

The PIC compiler options were never standards compliant up until around when Microchip purchased AVR. There are great chips now that have free gcc support, reasonable power draw, and 32bit float support (ATSAM3X8E current prices are not worth it in many cases.)

PIC does still have a few key use-cases, but most people will hit the stack depth limits pretty quickly in C. A pic12 Assembly project is fun, but the limitations cut deep these days.

STM32/ESP32/RP2350 or nRF for low power stuff are far less effort these days, and give much better value. =3

by dmitrygr5 hours ago|

prev|

[-]

SDCC has the best OSS 8051 compiler. It is buggy as hell, but it is free. Sometimes that is good enough.

by nickcw20 minutes ago|

parent|

[-]

I used sdcc for an 8051 based commercial project a while back. I seem to remember spending more time reading the assembly to figure out workarounds for the compiler than actually writing C code!

Whereas sdcc works brilliantly for z80 lineage processors. I wrote quite a lot of C for Gameboy recently and didn't find a single compiler bug in sdcc which revised my opinion of it upwards greatly.

by hacker_homie4 hours ago|

parent|

prev|

[-]

I used it for some toy projects never ran into "bugs" as in this is just broken, but it's quirky for sure.

by dmitrygr4 hours ago|

parent|

[-]

when you have large code, bugs will find you. for example two uint16 vars globally declared one after another. adding them together to each other will produce an access to garbage memory after 5-6 additions. dumb code but a simple repro. i ran into its bug when working on eInk price tags a while back.

by raphman3 hours ago|

parent|

[-]

As a student, 20 years ago, I felt like I was going crazy when using SDCC for pic16. Being new to microcontrollers and C, SDCC seemed cursed - even simple 'blink LED' test cases pseudo-randomly worked or didn't. It turned out that the compiler optimized away some 'empty' loops a little bit too aggressively without realizing that these loops were setting output pins. These bugs have long been fixed but still live on in my long-term memory.

by lelanthran2 hours ago|

parent|

[-]

> that the compiler optimized away some 'empty' loops a little bit too aggressively without realizing that these loops were setting output pins.

Doesn't sounds like a bug in the compiler, sounds more like `volatile` was not used (unless, of course, `volatile` was not being honoured).

by technothrasher2 hours ago|

parent|

prev|

[-]

I still run across this to this day with GCC and Cortex-M code. The optimizer will occasionally decide to blow away loops that are clearly doing something.

by uecker2 hours ago|

parent|

[-]

Please file a bug report, if you haven't done so.

by Jyaif2 hours ago|

parent|

prev|

[-]

What a coincidence, just yesterday I asked an LLM to generate a C compiler for the 8051 because SDCC's output was not optimized. Within an 1.5 hour it was correctly compiling my project at 60% of the size of what SDCC generates. One or 2 quota refreshes later it passed the SDCC test suite and optimized soft floats.

https://github.com/jyaif/cc51

by oasisaimlessly2 hours ago|

parent|

[-]

I assume you're running that test suite using a 3rd party 8051 emulator to avoid the potential for common-mode errors in both your compiler and emulator resulting in false confidence the compiler's correctness?

> two simulators used for testing, sim51 (a plain 8051) and minitel_sim

Narrator: No, he was not.

by Jyaif1 hours ago|

parent|

[-]

"it runs on my device" is my criteria of success here

by MobiusHorizons4 hours ago|

prev|

[-]

Has worked well enough for me on 8051 and stm8

by fiatpandas5 hours ago|

prev|

[-]

TIL about Dallas Semiconductor from this page.

Love Silicon Prairie lore.

by 2 hours ago|

prev|

[-]

deleted