[gccsdk] C++ and malloc

John Tytgat John.Tytgat at aaug.net
Mon May 19 22:17:54 BST 2008

In message <c88117a24f.Jan-Jaap at iyonix.c2i.net>
          Jan-Jaap van der Geer <janjaap at dsv.nl> wrote:

> Talking about libstdc++, I assume using the standard C++ classes
> (string, iostream, stl) means the resulting executable becomes
> dependent on SharedUnixLib? Looking at the info on riscos.info I
> could not find anything to suggest that this is the case.
> I did find references that it was possible to compile/link with
> -mlibscl, but apparently that did not mean that UnixLib is *not*
> used.
> In hindsight that seems reasonable, since SCL almost certainly does
> not know anything about these C++ classes, but it surprised me
> initially.

With GCCSDK 3.4.6 you can compile your C++ code with UnixLib or
SharedCLibrary as runtime library and the latter both for application
code and module code.

For GCCSDK 4.1.1, C++ code can only be compiled with UnixLib as runtime
library at the moment.  I haven't found the time to try this with the

John Tytgat, in his comfy chair at home                                 BASS
John.Tytgat at aaug.net                             ARM powered, RISC OS driven

More information about the gcc mailing list