Changeset 6ae41fd in rtems for c/PROBLEMS


Ignore:
Timestamp:
Sep 30, 1996, 8:07:07 PM (24 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
348ba42
Parents:
caf87fd7
Message:

updated for Release 3.6.0 to reflect status of posix threads.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • c/PROBLEMS

    rcaf87fd7 r6ae41fd  
    55This is the list of outstanding problems in this release.
    66
    7 +   The POSIX threads and real time extensions code in this tree are
    8     not completely tested yet.  Some of the POSIX tests do run but none
    9     of the POSIX code is in the normal build path.
     7+   The POSIX threads and real-time extensions are tested but this is
     8    the first release with them included.  They are not enabled by
     9    default.  The environment variable RTEMS_HAS_POSIX_API must be
     10    set to "yes" and the C language macro RTEMS_POSIX_API must be defined
     11    before this api is included in the build.
    1012
     13+   The shell scripts runtest and difftest do not work properly when
     14    testing "debug" executables.
     15
     16+   AMD 29k port is based on a non-GNU toolset.
     17 
    1118+   The test spfatal is out of date and as a result will NOT execute
    1219    correctly.  The addition of POSIX and consequent ongoing initialization
     
    2936    It is better to define these in the linkcmds file.  It is also nice
    3037    to use the linkcmds file to place overlays for on-board hardware.
     38
     39+   The __read(), __write(), etc. routines should be renamed __rtems_read(),
     40    etc. to avoid potential naming conflicts.  [NOTE: This is already
     41    necessary under some versions of Linux with the unix port.]
    3142
    3243+   The __read() system call in all of the BSPs using single
Note: See TracChangeset for help on using the changeset viewer.