Re: [Sdcc-user] printf_large flaoring suppost in libsdcc.lib

[Frieder F. <fri...@we...>]

Borut Razem schrieb:
> I and Maarten Brock had a discussion and agreed to enable the floating 
> point support in printf_large() function included in libsdcc.lib 
> library, which is a part of sdcc distribution, for large, 
> large-stack-auto, small-xstack-auto, medium-xstack-auto and 
> large-xstack-auto models for msc51 target.
> 
> If you have any objection against this decision, please let me know ASAP.

Ooops, I'd prefer rather not to. And think I have some objections:)


a) I think the increased resource usage will be seen as a major
regression for users

- migrating from earlier versions of SDCC to 2.9.x versions
  (with one of these memory models). Expect postings like:
  "using latest version of SDCC significantly increased code size"

- migrating from small memory models to one of the larger
  models will result in an disproportionate code memory increase
  being seen.

- migrating from other compilers towards SDCC.
  Note, for the other compiler the source might fit into
  small memory model while SDCC might require large model
  so the size difference can be so Huge as to be discouraging.
  "the evaluation version of the commercial compiler allowed only
  4 kByte code. To see whether SDCC would be an option I threw the
  code at SDCC, couldn't use the small memory there and ended up with
  x kByte - giving up."


b) Additionally I do not like the thought of functionality being
changed just because the memory model is switched
(should be as orthogonal to anything as can be).
"... switched to small memory model and my floating point
application ..."


c) Plus there is a reasonably friendly printf output: "<no float>"
in case of the non-floating point version of printf being
used for floats. (we hardly can warn the other way round)


Could there be a compiler option like -lPleaseLinkFloatingPointPrintf
which would we could point users seeing "<no float>" to?
No perceived regression, just an easy to communicate convenience
feature added?


Greetings,
Frieder