In message <[email protected]>
Lee Noar <[email protected]> wrote:
> On 28/08/11 17:18, Terje Slettebø wrote:
> > I've tried this too, and, yes, it works: I can use the vector in
> > those functions, now, thanks! :)
> >
> > I also tried this (instead of the <stdio.h> header):
> >
> > #include <iostream>
> >
> > std::cout << "Test"; // Inside gccmodule_init()
> >
> > but that crashed ("Abort on data transfer at &20AB2ACC9"). The
> > original puts() works, though. I wonder why. Maybe there's a
> > difference between how GCC handles C/C++ I/O.
>
> Hmm, this one may take more time. Unfortunately, I probably wont be able
> to fix this before I go on holiday, but I will take a look when I get
> back.
FYI, I never tried to use STL for C++ coded modules so I'm not surprised
there are some interesting things to be fixed there ;-)
> V4.6 fails to link with an undefined reference to strtof.
The gdtoa routines are not included in the SCL multilib variant. Something
to try out if this is possible to do so.
BTW I've disabled the use of all LGPL code in GCCSDK 4.6 UnixLib's SCL
multilib variant because we didn't do that in earlier GCCSDK releases.
So that also means that the -mlibscl built modules/applications don't have
any LGPL obligations.
However, those LGPL functions are still declared in our public headers
when -mlibscl use used, hence libraries (like libstdc++) still think they
can use such functions. So something else to be taken care of.
> > Regarding version 4.6: It appears that only version 4.1.1 (?) is
> > still available for download, is that right?
> > (http://www.riscos.info/packages/DevelopmentDetails.html#gcc4)
>
> Yes, v4.1.1 is the current release version, v4.6 is the development
> version at trunk. Anyone can try v4.6, but you have to build it
> yourself. The native compiler has only just recently become usable and
> has had very little testing. V4.6 uses an improved shared library system
> that is not compatible with earlier versions.
>
> > Is there any timeframe for a new release?
>
> I believe John is planning a v4.1.2 release next, but there is no
> specific time frame.
I really would like to have an asasm available in v4.1.2 which is
capable of building the RISC OS kernel. It is (was ?) far more work
than I anticipated but I believe I'm very close now with my latest
work on
http://www.riscos.info/websvn/listing.php?repname=gccsdk&path=%2Fbranches%2Fdevelopers%2Fjoty%2Fasasm-twopass%2F&#a3588045be84b41938e114c7ab2acbf8d
BTW, if someone wants to try out and/or help, feel free to contact me.
John.
--
John Tytgat, in his comfy chair at home BASS
[email protected] ARM powered, RISC OS driven
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
