> > >> >> >> I have cloned this NetBSD Sources. As I can see those >> >> architecture-specific implemented methods here. Please correct me if I >> >> am looking into different than what you are looking for. >> >> >> >> ./lib/libm/arch/powerpc/fenv.c >> >> ./lib/libm/arch/sh/fenv.c >> >> ./lib/libm/arch/mips64/fenv.c >> >> ./lib/libm/arch/amd64/fenv.c >> >> ./lib/libm/arch/arm/fenv.c >> >> ./lib/libm/arch/i387/fenv.c >> >> ./lib/libm/arch/hppa/fenv.c >> >> ./lib/libm/arch/m88k/fenv.c >> >> ./lib/libm/arch/alpha/fenv.c >> >> ./lib/libm/arch/sparc64/fenv.c >> >> ./lib/libm/arch/aarch64/fenv.c >> >> ./regress/lib/libm/fenv/fenv.c >> > >> > >> > That's what I see browsing the repo. >> > >> > The single file NetBSD looks easy to integrate. Would be similar to the >> x86_64 or i386 there now on file layout. >> > >> > Does the freebsd support more hardware variants? >> >> FreeBSD does not have fenv support for some architecture like RISCV, >> M88k, alpha architecture, I can see netbsd support more >> hardware variants. NetBSD includes fenv support for these architecture >> also. >> > > +1 > > NetBSD has more architectures and looks easier to integrate. But we need > to be > sure the NetBSD implementation for an specific architecture covers all the > cases > that FreeBSD does. If equal, pick the more that is easier to integrate. > > --joel > Last year I found various sources: https://lists.rtems.org/pipermail/devel/2019-July/026580.html
https://lists.rtems.org/pipermail/devel/2019-July/054391.html --Vaibhav
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel