From ac7d5ef06a6d6e8d84abbd1f0b82162725f98326 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Thu, 11 May 1995 17:39:37 +0000 Subject: Initial revision --- c/PROBLEMS | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 c/PROBLEMS (limited to 'c/PROBLEMS') diff --git a/c/PROBLEMS b/c/PROBLEMS new file mode 100644 index 0000000000..b8e75dc58b --- /dev/null +++ b/c/PROBLEMS @@ -0,0 +1,39 @@ +# +# $Id$ +# + +This is the list of outstanding problems in this release. + +1. The m68000 support is not complete. Someone with target hardware + needs to complete the missing gaps. Look for ifdef's based on the + M68K_* macros defined in c/make/cpu/m68k.cfg. Most of the code + is present but none of it is tested. An attempt was made to insert + "#warnings" preprocessor directives in the appropriate places. + So these are a good starting spot. + +2. The only i960 family member tested is the CA. No support for the + floating point support found in other family members is present. + This also implies that RTEMS may "think" of something as generic + across the i960 family when in fact it is specific to the CA. + +3. 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: + + + echoing of characters on input + + CR/NL echoing + + backspaces + + tabs + +4. Solaris 2.3 port notes: + + + Some of the tests run correctly when run interactively but + the screen and output do not match when the output is + redirected to a file. + + + sometimes a stray SIGALRM is reported as spfatal completes. + +5. Some of the tests may execute correctly and not produce the exact + ordering of lines in the screen file. This appears to be a combination + of a number of factors including buffering, processor speed, IO + device overhead, and clock interrupt rate. -- cgit v1.2.3