search for: int_least8_t

...efine a byte to be e.g. 16 bits wide, does it mean that > "char" is also 16 bits wide? If yes then how to do you define types > like int8_t from stdint.h? Yes, char is the same. The int8_t type is optional according to the standard and we don't define it for our OOT target. The int_least8_t is required, but we just define it to be byte sized. > 3. Have you thought about the possibility to support different byte > sizes for data and code? Not really, but I saw that Jeroen Dobbelaere just suggested supporting memory spaces with different byte sizes. > 4. I realize that this...

> OK, attempting one more convergence on all this, here's > what I did: > > 1. Reverted back to rev 1.5 of src/libFLAC/ia32/Makefile.am > 2. Applied Matt's last cleanup patch of 8 files. I did not > apply the patch to src/test_unit/main.c since it looks wrong. > main.c is supposed to include the local bitbuffer.h, not > src/libFLAC/private/bitbuffer.h; I think the

A. This RFC outlines a proposal regarding non-8-bit-byte support that got positive reception at a Round Table at EuroLLVM19. The general topic has been brought up several times before and one good overview can be found in a FOSDEM 2017 presentation by Jones and Cook: https://archive.fosdem.org/2017/schedule/event/llvm_16_bit/ In a nutshell, the proposal is for the llvm community