Cross gcc Mailing List Archive
[Prev][Next][Index][Thread]
rtems 3.6.0 announcement
I thought this might be of interest to the readers of
this list. :)
--joel
November 13, 1996
RTEMS User,
We are pleased to announce the availability of RTEMS 3.6.0, a standard
release. Support and training are available from On-Line Applications
Research Corporation. Email rtems@OARcorp.com for information.
If you are an Ada user please continue to use version 3.2.1 of RTEMS, this
new release only addresses the C community at this time.
This release will be available via anonymous ftp from /pub/rtems on
ftp.rtems.army.mil. In addition, the RTEMS Home Page will be
updated to include the new version.
New in 3.6.0:
RTEMS has been enhanced and modified in efforts to support a GNAT Ada Runtime
and POSIX threads and runtime extensions. This effort is unfinished at this
time. Enough of the POSIX functions are implemented and tested to support
the GNAT Ada Runtime. Development will continue on POSIX API support and
an associated test suite.
RTEMS development is in a feature addition mode. Performance will
probably be negatively impacted (we hope slightly) until the POSIX
API is complete and tuning can begin. If you notice an area where we
could shave a significant amount of time off, let us know. We honestly
have not looked closely at execution times.
The following enhancements and modifications have been made to RTEMS since
version 3.5.1:
CODE and DEVELOPMENT ENVIRONMENT
==========================================================================
+ Implemented "priority_ceiling" protocol for both rtems semaphores and
posix mutexes.
+ Continued enhancement of the template file for the RTEMS configuration
tables. This is in src/tests/include/confdefs.h. It is highly
recommended that applications use this file to define their configuration
files as it insulates them from version changes.
+ newlib rtems support was reimplemented to add posix api support.
+ We now assume that you are using the CPU-rtems configurations
for the gnu tools and rtems. This allows the one tree build
instructions in the crossgcc faq to be used to build an rtems
development environment. The current release of gcc (2.7.1.1)
does not have these although the next major gcc release should.
+ make files cleaned up.
+ single library now built by merging libbsp, libmisc, libcpu, and librtems.
This simplified the link order for the tests and for most applications.
+ added user extension to allow bsp to allocate and deallocate task stacks
+ modifications to avoid use of GNU C specific extensions.
+ modifications to support CPUs with 64-bit integers and 32-bit pointers.
PORTS, BSPs, and HOSTs
==========================================================================
+ Addition of the SPARC port. This effort was performed by On-Line
Applications Research Corporation under contrac to the European Space
Agency.
+ Addition of the MIPS and AMD 29K ports. These were performed by
Craig Lebakken (lebakken@minn.net) and Derrick Ostertag
(ostertag@transition.com) of Transition Networks.
+ Addition of the following user submitted BSPs:
- gen68360 by Eric Norum (eric@skatter.usask.ca) of the
Saskatchewan Accelerator Laboratory
- mvme147 and mvme147s by Dominique le Campion
(Dominique.LECAMPION@enst-bretagne.fr), of Telecom Bretagne
and T.N.I. (Brest, France)
+ NextSTEP 3.0 host support was submitted by Eric Norum
(eric@skatter.usask.ca) of the Saskatchewan Accelerator Laboratory
The RTEMS project uses SparcStations running the Solaris 2.3 operating
system internally. This release has been tested on the following
Languages/CPUs/Targets using Solaris 2.3/SPARC as the host environment:
CPU CPU
LANGUAGE FAMILY MODEL TARGET SUITES
======== ====== ========= =================== ===============
C a29k a29205 portsw (note 2)
C m68k m68000 efi68k (note 1)
C m68k m68020 DY-4 DMV152 (note 1)
C m68k m68020 Motorola MVME136 (note 5)
C m68k m68030 Motorola MVME147 (note 1)
C m68k m68030 Motorola MVME147s (note 1)
C m68k m68lc040 Motorola MVME162 (note 1)
C m68k m68ec040 Motorola IDP (note 1)
C m68k m68302 generic 68302 (note 1)
C m68k m68302 generic 68360 (note 1)
C m68k m68332 efi332 (note 1)
C i386 i386_fp Force CPU-386 ALL TESTS
C i386 i486 DJGPP/PC-AT ALL TESTS
C i386 pentium DJGPP/PC-AT ALL TESTS
C i960 i960ca Cyclone CVME961 (note 5)
C hppa hppa7100 simhppa (note 1)
C mips64 r4600 p4000 (note 1)
C mips64 r4650 p4000 (note 1)
C ppc 403 Papyrus (note 1)
C sparc erc32 sis (note 4)
C UNIX NA Solaris 2 (SPARC) ALL TESTS (inlines)
C UNIX NA Solaris 2 (SPARC) ALL TESTS (macros)
C UNIX NA Linux (i386) NOT TESTED
C UNIX NA HPUX (PA-RISC) (note 2)
C no_cpu NA no_bsp (note 3)
NOTES:
(1) Target board is not owned by RTEMS Project. The target is known
to compile and link with all appropriate tests successfully.
If the target does not support multiprocessor configurations, then
"ALL TESTS" does not include the multiprocessor tests.
(2) RTEMS Project cannot internally compile or test this target.
(3) Target is not intended to be executed. It is only an example.
(4) sis is the SPARC Instruction Simulator. It is available from
ftp.estec.esa.nl in the /pub/ws/wsd/erc32 directory.
(5) The RTEMS Project owns this board but it is broken at the moment.
RTEMS was developed by On-Line Applications Research (OAR) Corporation
(http://www.oarcorp.com) under contract to the Research, Development,
and Engineering Center of the U.S. Army Missile Command.
RTEMS is provided as a Technology Transfer/Dual Use service to
individuals and companies having a need for this product. The RTEMS
source and necessary development environment is available by the
appropriate references below. RTEMS can be retrieved either through
anonymous ftp at ftp.rtems.army.mil in the /pub/rtems directory or
through the WWW at http://www.rtems.army.mil/rtems.html.
Home |
Subject Index |
Thread Index