From 6ae41fd03524e7021d28e58f6e0af508a9f8cd06 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Mon, 30 Sep 1996 20:07:07 +0000 Subject: updated for Release 3.6.0 to reflect status of posix threads. --- c/PROBLEMS | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) (limited to 'c/PROBLEMS') diff --git a/c/PROBLEMS b/c/PROBLEMS index 576e197380..f09a9b04f6 100644 --- a/c/PROBLEMS +++ b/c/PROBLEMS @@ -4,10 +4,17 @@ This is the list of outstanding problems in this release. -+ The POSIX threads and real time extensions code in this tree are - not completely tested yet. Some of the POSIX tests do run but none - of the POSIX code is in the normal build path. ++ The POSIX threads and real-time extensions are tested but this is + the first release with them included. They are not enabled by + default. The environment variable RTEMS_HAS_POSIX_API must be + set to "yes" and the C language macro RTEMS_POSIX_API must be defined + before this api is included in the build. ++ The shell scripts runtest and difftest do not work properly when + testing "debug" executables. + ++ AMD 29k port is based on a non-GNU toolset. + + The test spfatal is out of date and as a result will NOT execute correctly. The addition of POSIX and consequent ongoing initialization reorganization makes it pointless to fix this until the POSIX support @@ -29,6 +36,10 @@ This is the list of outstanding problems in this release. It is better to define these in the linkcmds file. It is also nice to use the linkcmds file to place overlays for on-board hardware. ++ The __read(), __write(), etc. routines should be renamed __rtems_read(), + etc. to avoid potential naming conflicts. [NOTE: This is already + necessary under some versions of Linux with the unix port.] + + The __read() system call in all of the BSPs using single character input/output needs to be smarter. The following issues need to be addressed: -- cgit v1.2.3