On Sun, Apr 10, 2016 at 1:24 AM Joel Sherrill <j...@rtems.org> wrote:
> > > On Sat, Apr 9, 2016 at 10:17 AM, Daniel Gutson < > daniel.gut...@tallertechnologies.com> wrote: > >> >> El 9/4/2016 12:15, "Joel Sherrill" <j...@rtems.org> escribió: >> > >> > Hi >> > >> > These are the BSPs which do not build all tests with C++ and the >> in-tree network stack enabled: >> > >> > + epiphany_sim - GCC ICE building mongoose.c. No investigation. >> > Gcc 6? Could you please attach more data, such as the gcc output and the >> test? >> >> Most targets are like this: > > arm-rtems4.12-gcc (GCC) 6.0.0 20160327 (RTEMS 4.12, RSB > 648e2d5d6c308227c456434238da5f3f881bddc7, Newlib 2.4.0) > > But epiphany hasn't been merged yet and has its own issues: > > epiphany-rtems4.12-gcc (GCC) 4.9.0 20140411 (RTEMS 4.12, RSB > 648e2d5d6c308227c456434238da5f3f881bddc7, Newlib > 8b1ede3ce11d53292036aadfcfb6043df0235f9c) > > I can post the ICE but not even sure what good it would do. > > >> > >> > + m32c - does not even build a C++ compiler. This is a small CPU and >> there isn't any general support for C++. This was why it was on my list of >> automatically disabled. >> >> This is gcc 6. And I think we just disable C++ for m32c. > > >> > + moxiesim - cxx_iostream.exe fails to link bcause it can't find >> __dso_handle. I don't know if C++ works for moxie-elf or if this is RTEMS >> specific. >> > This is gcc 6. It has had this issue for months. I don't think C++ has > ever worked. > I have investigated but don't have a clue which tiny bit is wrong. > > >> > + or1k - needs newlib bumped to match tree. >> > or1k was also using older gcc 4.9.3. It hasn't been merged yet. I am > updating it > now to the latest newlib. > > I have a pending submitted patch for or1k tools. It needs to be merged in order for rtems-or1k to compile. I can't merge it because I've issues with my old SSH key and laptop, so please merge it. > > + sh/gensh4 - undefined reference to __gnu_cxx::__atomic_add(int >> volatile*, int) in cxx_iostream test >> >> This is gcc 6. It has had this issue for months. It broke when the atomic > changes > and our C++ configuration changed. I have investigated but don't have a > clue > which tiny bit is wrong. > > > >> > --joel >> > >> > _______________________________________________ >> > devel mailing list >> > devel@rtems.org >> > http://lists.rtems.org/mailman/listinfo/devel >> >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
