|
From: Andrew J. <an...@ap...> - 2013-02-20 15:54:31
|
Hi Marty, On 2013-02-20 Marty Kraimer wrote: > > Is there any chance that we can try to allow full use of the c++11 > standard on all supported platforms? Not if you're wanting to support vxWorks. Even the latest vxWorks 6.9 only has gcc 4.3.3. (vxWorks 6.8 comes with gcc 4.1.2) > You have as the supported platforms: > > Platforms Supported > > > > The following platforms are actively supported and tested: > > > > * GNU/Linux on x86_64 > > * vxWorks >= 6.6 on PowerPC or Intel CPUs We're waiting for feedback on that from PSI, from either Dirk or Timo. > I also have a question about how current vxWorks implementations > implement new. > Do current implementations have a good way to handle the heap? > In the past the implementation caused severe memory fragmentation, which > could be a show stopper for using the c++ standard library. The system memory allocator in vxWorks 6.x uses a best fit algorithm so should not be subject to the memory fragmentation issues that the first fit code in vxWorks 5.x suffered from. Not tested, but I don't really know how to do that anyway... > What about RTEMS? RTEMS 4.10 builds using gcc 4.4.6 - Andrew -- There is no such thing as a free lunch. When invited for lunch, it is best to check if you are there to eat, or to be eaten. -- Clive Robinson |