Changeset 8a7fafb3 in rtems for c/PROBLEMS


Ignore:
Timestamp:
Apr 23, 1997, 6:17:01 PM (23 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
18647b7
Parents:
7346e5f
Message:

Updated to reflect changes since 3.6.0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • c/PROBLEMS

    r7346e5f r8a7fafb3  
    44
    55This is the list of outstanding problems in this release.
    6 
    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.
    126
    137+   The shell scripts runtest and difftest do not work properly when
     
    3731    to use the linkcmds file to place overlays for on-board hardware.
    3832
    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.]
    42 
    4333+   The __read() system call in all of the BSPs using single
    4434    character input/output needs to be smarter.  The following
     
    5646       + There are conflicts between the names of native library routines
    5747         which MUST be used and those in the POSIX support.  This must
    58          be addressed.
     48         be addressed.  The POSIX API cannot be used with this port as a
     49         result of this.
    5950
    6051+   Some of the tests may execute correctly and not produce the exact
     
    6354    device overhead, and clock interrupt rate.
    6455
    65 +   The compiler configuration files (c/make/gcc-XYZ.cfg) are largely
    66     the same when the different targets have the same CPU.  It would
    67     be desirable to have a gcc-CPU.cfg or gcc-CPU_MODEL.cfg (e.g.
    68     gcc-m68k.cfg or gcc-m68020.cfg) and have the file gcc-TARGET.cfg
    69     include this and possibly override default settings.
    70  
    7156+   The clock device drivers should really avoid doing the division
    7257    by 1000 in the clock tick ISR to convert microseconds into
Note: See TracChangeset for help on using the changeset viewer.