This is the mail archive of the
mailing list for the newlib project.
RE: Newlib : stdio : fprintf and sprintf - not faulty - buffer-based pipes needed.
- From: "Bin Cheng" <bin dot cheng at arm dot com>
- To: "'J.B.W.Webber'" <J dot B dot W dot Webber at kent dot ac dot uk>, <newlib at sourceware dot org>
- Date: Thu, 13 Jun 2013 17:35:29 +0800
- Subject: RE: Newlib : stdio : fprintf and sprintf - not faulty - buffer-based pipes needed.
- References: <2CF6002E09D8F54E9839DA08786D3200958D2A91 at EX10-LIVE-MBN2 dot ad dot kent dot ac dot uk> <2CF6002E09D8F54E9839DA08786D3200958D4768 at EX10-LIVE-MBN2 dot ad dot kent dot ac dot uk>
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org] On
> Behalf Of J.B.W.Webber
> Sent: Wednesday, June 12, 2013 6:45 PM
> To: email@example.com
> Subject: RE: Newlib : stdio : fprintf and sprintf - not faulty -
> pipes needed.
> My apologies,
> I have no idea at the moment why fprintf was not outputting, in the
> e-run simulator, for Parallella-Linux generated code for the Epiphany.
> However sprint in the code, run actually on the Epiphany cores, does
> fine, correctly outputting to the communication buffer. i.e. :
> 0: Message from eCore 0x8ca ( 3, 2): "some text Qsome text 1 2 3 4 5 6 7
> 1: Message from eCore 0x84b ( 1, 3): "some text Qsome text 1 2 3 4 5 6 7
> The problem was a too-short delay before the Linux host read the buffer.
> a very crude temporary interface.
> Thus this aplc APL to C code translator is at least partially ported to
> Parallella and Epiphany cores.
> If anyone knows how to create Std-in Std-out (and generic pipes) based on
> buffers on the Epiphany chip, with proper synchronisation, I would much
> appreciate receiving comments, examples or working code. This exceeds my
> remaining knowledge of c (~1980 - ~1990) or my understanding of newlib.
Both the problem and system are beyond my knowledge and I don't have answer
for it. Maybe you can re-build newlib (even with -O0) and debug it along
with your application. I have much confidence in fprintf implementation of
newlib (since it works elsewhere), so I suspect the problem might be in
application-library interface or something like that.