From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: RFC: Changing daddr_t to 64 bits
Date: Mon, 26 Oct 2020 11:53:51 +0100 [thread overview]
Message-ID: <20201026105351.GC5492@calimero.vinschen.de> (raw)
In-Reply-To: <20201026095752.GB5492@calimero.vinschen.de>
On Oct 26 10:57, Corinna Vinschen via Newlib wrote:
> 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.
^^^^^
Probably better newlib/libc/sys/rtems/include/sys/types.h
Sorry,
Corinna
prev parent reply other threads:[~2020-10-26 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 21:43 Joel Sherrill
2020-10-26 9:57 ` Corinna Vinschen
2020-10-26 10:53 ` Corinna Vinschen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201026105351.GC5492@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).