Hi,
The typedef for d_size_t assumes that the implementation of the
front-end is written in D itself, where size_t can map only to uint32_t
or uint64_t. As that is not the case for the current D front-end, the
typedef should be removed. This would fix the bootstrap on targets where
in C++ size_t
Iain Buclaw via Gcc-patches wrote:
The typedef for d_size_t assumes that the implementation of the
front-end is written in D itself, where size_t can map only to uint32_t
or uint64_t. As that is not the case for the current D front-end, the
typedef should be removed. This would fix the bootstr
Excerpts from Iain Sandoe's message of November 29, 2020 1:54 pm:
> Iain Buclaw via Gcc-patches wrote:
>>
>> The typedef for d_size_t assumes that the implementation of the
>> front-end is written in D itself, where size_t can map only to uint32_t
>> or uint64_t. As that is not the case for the c
