> Technically resource_pool is relying on non-portable behavior, but fixing it the
> "right" way would mean rearranging a bunch of the memory allocation code so that the
> memory_entry gets populated after g++ fixes up the pointer. Or just do the simple
> workaround -- add an ARM-specific #ifdef that uses 8 instead of sizeof(size_t), and
> cross your fingers that g++ never needs padding on other platforms.
resource_pool just went away entirely, so 0.153 should be safe for ARM.
|
Previous 
Index 
Next 
Flat 
Re: mame 0152 running on ARM produces segmentation fault
Reply
