Basil Hussain

Maybe it has something to do with how it is compiled. Perhaps the access violation is only thrown when compiled in Debug mode? Or maybe it's an x64 thing? Or...

Hmm, but array indices are treated as _unsigned_, and 0x5000 is being _subtracted_ from 0xFFFFFFFF, so I don't understand how that out-of-bounds access (to index 0xFFFFAFFF of an array whose...

I did a test of real hardware (an STM8S208RB) versus the emulator. I wrote the following test program: ```c // Compile with: sdcc -mstm8 --out-fmt-ihx -o "adc_test.hex" main.c #include #define...

> ideally some kind of backward compatibility inside SDCC itself? I would predict that it's unlikely. Unfortunately for the PDK platform, the init code is generated by the compiler, rather...

I would like to also add my support for an addition to the API specification for an ability to change an open port's configuration - particularly the baud rate -...

There is definitely a bug with saving and restoration of the window size between uses. This bug still persists in version 0.17.1. Every time MarkText is launched, the window grows...

I tried the v0.6.6-alpha release for CH32V003 on a dev board, but it doesn't work. Nothing is output on the UART. I don't think you are configuring the UART correctly...

I've been looking into modifying the code to properly support the CH32V003. I've added some stuff to properly initialise RCC, GPIO, and UART (as per my previous comment). But I...

Upon further investigation, I think we have a more fundamental incompatibility with the CH32V003. There are various parts of the code that assume the presence of the standardised RISC-V interrupt...

> However the design of the POSIX and Windows APIs does not permit this (POSIX almost does) Ah, that's a shame. A cursory glance at the Windows API documentation for...