fseek() vs. fseeko()
Wed Jun 20 13:42:00 GMT 2012
On 06/19/2012 07:36 PM, Sebastian Huber wrote:
> On 19/06/12 19:11, Corinna Vinschen wrote:
>> On Jun 19 18:27, Ralf Corsepius wrote:
>>>> Ok, then this is a bug in the RTEMS targets using 64-bit off_t.
>>> No. This is a bug in newlib.
>>> fseeko etc. are supposed to take abstract types "off_t".
>>> RTEMS relies upon this assumption, but obviously can't handle this.
>>>> Since> the fseeko64() etc. are non-standard this should be
>>> invisible for the> user.
>>> Agreed. They should not be used anywhere and be removed from newlib.
>> That's obviously not possible for backward compatibility.
> I don't know if we can assume sizeof(off_t) >= sizeof(long). Suppose we
> can, then we may implement the fseek(), _fseek_r(), and fseeko() with a
> _fseeko_r(). The internal state seems to use the proper integer types.
Exactly. This is what I currently am working on. I have a patch, but it
currently is too rough for being published.
In case you are interested in testing, I could attach it to your RTEMS
BZ rsp. mail it on PM.
More information about the Newlib