search for: llvm_16_bit

...oment, we have a hacky implementation with a new byte size hardcoded. For a reference: the scope was to change approximately 20 files in LLVM and about a dozen in Clang. Later on, we plan to integrate the new byte size with data layout according to <https://archive.fosdem.org/2017/schedule/event/llvm_16_bit/> https://archive.fosdem.org/2017/schedule/event/llvm_16_bit/. And if the community decides to move on, we will upstream and maintain it. We realize that a 257 bits byte is quite unusual, but for smart contracts it is ok to have at least 256 bits numbers. The leading VM for smart contracts, Eth...

...egarding 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 to allow/encourage interested parties to gradually remove "magic numbers", e.g. assumptions on the size of bytes from the codebase. Overview, rationale and some example refactorings follows. Overview: LLVM currently assumes 8-bit b...

Hi, I'm with a team using 16-bit bytes for an out-of-tree target. The AsmPrinter framework's implementation of the DWARF debugging format is not very good at distinguishing between target-sized bytes (which is the more common use) and 8-bit-bytes. The DWARF standard itself seems not very good in this regard, actually. So we have had to hack our way around this. I.e., at some call-sites of

...itive 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 to > > allow/encourage interested parties to gradually remove "magic > > numbers", > > e.g. assumptions on the size of bytes from the codebase. Overview, > > rationale and some example refa...

...n brought up several times before and one good > > overview > > can be found in a FOSDEM 2017 presentation by Jones and Cook: > > https://protect2.fireeye.com/url?k=2d1c7421-7195ae31-2d1c34ba-0cc47ad93e2a-4cae3fa5d066a45a&u=https://archive.fosdem.org/2017/schedule/event/llvm_16_bit/ > > > > In a nutshell, the proposal is for the llvm community to > > allow/encourage interested parties to gradually remove "magic > > numbers", > > e.g. assumptions on the size of bytes from the codebase. Overview, > > rationale and some example refa...