Changeset 3b1c100 in rtems for cpukit/score/cpu/no_cpu


Ignore:
Timestamp:
Sep 26, 2003, 9:56:41 PM (17 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, master
Children:
1aa101b
Parents:
d956ef7
Message:

2003-09-26 Joel Sherrill <joel@…>

  • rtems/score/cpu.h: Obsoleting HP PA-RISC port and removing all references.
Location:
cpukit/score/cpu/no_cpu
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • cpukit/score/cpu/no_cpu/ChangeLog

    rd956ef7 r3b1c100  
     12003-09-26      Joel Sherrill <joel@OARcorp.com>
     2
     3        * rtems/score/cpu.h: Obsoleting HP PA-RISC port and removing all
     4        references.
     5
    162003-09-04      Joel Sherrill <joel@OARcorp.com>
    27
  • cpukit/score/cpu/no_cpu/rtems/score/cpu.h

    rd956ef7 r3b1c100  
    193193 *  If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
    194194 *
    195  *  So far, the only CPU in which this option has been used is the
    196  *  HP PA-RISC.  The HP C compiler and gcc both implicitly use the
    197  *  floating point registers to perform integer multiplies.  If
    198  *  a function which you would not think utilize the FP unit DOES,
     195 *  So far, the only CPUs in which this option has been used are the
     196 *  HP PA-RISC and PowerPC.  On the PA-RISC, The HP C compiler and
     197 *  gcc both implicitly used the floating point registers to perform
     198 *  integer multiplies.  Similarly, the PowerPC port of gcc has been
     199 *  seen to allocate floating point local variables and touch the FPU
     200 *  even when the flow through a subroutine (like vfprintf()) might
     201 *  not use floating point formats.
     202 *
     203 *  If a function which you would not think utilize the FP unit DOES,
    199204 *  then one can not easily predict which tasks will use the FP hardware.
    200205 *  In this case, this option should be TRUE.
Note: See TracChangeset for help on using the changeset viewer.