4 ms·
I wrote 16 when I meant 8bits. For this arch you cannot have 8 but types. Casting a int16_t* to char* won't let you access upper and lower bytes as most people
by btashton 8y ago
I wrote 16 when I meant 8bits. For this arch you cannot have 8 but types. Casting a int16_t* to char* won't let you access upper and lower bytes as most people would except (c standard does not define this behavior).
- yorwba 8y agoWhat happens if you use uint8_t in a C program on XAP? Does the compiler emulate 8-bit values using 16-bit fields or is there simply no support for such a type? FWIW, https://www.cambridgeconsultants.com/xap https://www.cambridgeconsultants.com/xap claims support for 8-bit datatypes, but offers further documentation only by email.
- comex 8y agoNote that "XAP" refers to a whole range of processors with incompatible instruction sets; the latest is XAP6 [1]. [1] https://en.wikipedia.org/wiki/XAP_processor#History https://en.wikipedia.org/wiki/XAP_processor#History
- btashton 8y agoXAP2 you will still be allocating a 16bit value. So you if you create an array of 2 uint8 you will still be allocating 32bits of memory.