Re: RFC: Changing daddr_t to 64 bits

Corinna Vinschen via Newlib <[email protected]> Mon, 26 Oct 2020 10:57:52 +0100

Newsgroups	gmane.comp.lib.newlib
Message-ID	<[email protected]>

On Oct 25 16:43, Joel Sherrill wrote:
> Hi
> 
> The type daddr_t is defined to be long but per some IBM documentation, it
> is "used for disk addresses, except in i-nodes on disk. The
> */usr/include/sys/filsys.h* file format describes the format of disk
> addresses used in i-nodes."
> 
> RTEMS has this in our BSD derived code and 32-bits is too small for disk
> addresses. We need it to be 64-bits at least for us.
> 
> Can I change it to be 64-bits for all targets?

I don't think so.  The existing non-RTEMS definitions should stay
untouched for backward compat.  Noticable is phoenix, which defines
__daddr_t explicitely as __uint32_t.

AFAICS, RTEMS defines __daddr_t not at all.  Just define __daddr_t in
newlib/libc/sys/linux/sys/types.h should fix this up for you.

Thanks,
Corinna