Joel Sherrill commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5434#note_140946 Sorry in advance if I miss something. Important to note that @rurban is now on on the RTEMS GitLab and willing to mentor. **Configure safeclib Tests -** There is a default configuration library installed by all BSPs which you can use. (librtemsdefaultconfig.a). This is enough to link and run some tests. Very basic configuration. My [test helpers](https://gitlab.rtems.org/joel/rtems-testing-helpers) are old but have similar rtems config files to test gcc itself with. Also, there will eventually be two ways we want this configured/built. One is to build for a specific BSP. In that case you will need to specify the C flags and linker arguments in addition to the RTEMS config. I have attached a very simple example which shows how to use pkgconfig to get those from any BSP. This build way should work and with careful setting of parameters should let the tests run. **Float Support** - I see that newlib's isinfl() matches that of Linux but newlib's math.h has this: `#ifdef **CYGWIN** /* not implemented in newlib yet */` `extern int isinfl (long double); ` `extern int isnanl (long double); ` `#endif` The implementation for Cygwin is in _winsup/cygwin/math/isinf.c_ in the newlib source. Part of the project will be adding that to newlib for RTEMS (change that ifdef and possibly copy the winsup implementation to newlib). The alternative is changing safeclib not to use this non-standard function. Personally, I am happy either way. But the RTEMS philosophy leans to adding APIs which aid portability. Although non-standard, this falls into this bucket. So first build to target a specific BSP and test. Later build it multilib and add building it to the RTEMS Source Builder. **Upstream Bugs** - If these are in safeclib,@rurban is the ultimate answer but my advice would be to file issues and make specific pull requests on the safeclib repo with fixes. And remember, RTEMS has applied to GSoC but the participating organisations have not been announced. Keep track of what you are doing, have done, and have planned. That should be in your GSoC project proposal. [quick_pc.tar.bz2](/uploads/05d810148cb2731f36a5e280778b40ab/quick_pc.tar.bz2) -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5434#note_140946 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
