Changeset 3b1c100 in rtems


Ignore:
Timestamp:
Sep 26, 2003, 9:56:41 PM (18 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, 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
Files:
18 edited

Legend:

Unmodified
Added
Removed
  • cpukit/score/cpu/arm/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/arm/rtems/score/cpu.h

    rd956ef7 r3b1c100  
    163163 *  If TRUE, then the RTEMS_FLOATING_POINT task attribute is assumed.
    164164 *  If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
    165  *
    166  *  So far, the only CPU in which this option has been used is the
    167  *  HP PA-RISC.  The HP C compiler and gcc both implicitly use the
    168  *  floating point registers to perform integer multiplies.  If
    169  *  a function which you would not think utilize the FP unit DOES,
    170  *  then one can not easily predict which tasks will use the FP hardware.
    171  *  In this case, this option should be TRUE.
    172165 *
    173166 *  If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well.
  • cpukit/score/cpu/c4x/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/c4x/rtems/score/cpu.h

    rd956ef7 r3b1c100  
    204204 *  If TRUE, then the RTEMS_FLOATING_POINT task attribute is assumed.
    205205 *  If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
    206  *
    207  *  So far, the only CPU in which this option has been used is the
    208  *  HP PA-RISC.  The HP C compiler and gcc both implicitly use the
    209  *  floating point registers to perform integer multiplies.  If
    210  *  a function which you would not think utilize the FP unit DOES,
    211  *  then one can not easily predict which tasks will use the FP hardware.
    212  *  In this case, this option should be TRUE.
    213206 *
    214207 *  If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well.
  • cpukit/score/cpu/h8300/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/h8300/rtems/score/cpu.h

    rd956ef7 r3b1c100  
    171171 *  If TRUE, then the RTEMS_FLOATING_POINT task attribute is assumed.
    172172 *  If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
    173  *
    174  *  So far, the only CPU in which this option has been used is the
    175  *  HP PA-RISC.  The HP C compiler and gcc both implicitly use the
    176  *  floating point registers to perform integer multiplies.  If
    177  *  a function which you would not think utilize the FP unit DOES,
    178  *  then one can not easily predict which tasks will use the FP hardware.
    179  *  In this case, this option should be TRUE.
    180173 *
    181174 *  If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well.
  • cpukit/score/cpu/mips/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/mips/rtems/score/cpu.h

    rd956ef7 r3b1c100  
    183183 *  If TRUE, then the RTEMS_FLOATING_POINT task attribute is assumed.
    184184 *  If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
    185  *
    186  *  So far, the only CPU in which this option has been used is the
    187  *  HP PA-RISC.  The HP C compiler and gcc both implicitly use the
    188  *  floating point registers to perform integer multiplies.  If
    189  *  a function which you would not think utilize the FP unit DOES,
    190  *  then one can not easily predict which tasks will use the FP hardware.
    191  *  In this case, this option should be TRUE.
    192185 *
    193186 *  If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well.
  • cpukit/score/cpu/mips64orion/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/mips64orion/rtems/score/cpu.h

    rd956ef7 r3b1c100  
    182182 *  If TRUE, then the RTEMS_FLOATING_POINT task attribute is assumed.
    183183 *  If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
    184  *
    185  *  So far, the only CPU in which this option has been used is the
    186  *  HP PA-RISC.  The HP C compiler and gcc both implicitly use the
    187  *  floating point registers to perform integer multiplies.  If
    188  *  a function which you would not think utilize the FP unit DOES,
    189  *  then one can not easily predict which tasks will use the FP hardware.
    190  *  In this case, this option should be TRUE.
    191184 *
    192185 *  If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well.
  • 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.
  • cpukit/score/cpu/or32/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/or32/rtems/score/cpu.h

    rd956ef7 r3b1c100  
    189189 *  If TRUE, then the RTEMS_FLOATING_POINT task attribute is assumed.
    190190 *  If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
    191  *
    192  *  So far, the only CPU in which this option has been used is the
    193  *  HP PA-RISC.  The HP C compiler and gcc both implicitly use the
    194  *  floating point registers to perform integer multiplies.  If
    195  *  a function which you would not think utilize the FP unit DOES,
    196  *  then one can not easily predict which tasks will use the FP hardware.
    197  *  In this case, this option should be TRUE.
    198191 *
    199192 *  If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well.
  • cpukit/score/cpu/sh/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/sh/rtems/score/cpu.h

    rd956ef7 r3b1c100  
    147147 *  If TRUE, then the RTEMS_FLOATING_POINT task attribute is assumed.
    148148 *  If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
    149  *
    150  *  So far, the only CPU in which this option has been used is the
    151  *  HP PA-RISC.  The HP C compiler and gcc both implicitly use the
    152  *  floating point registers to perform integer multiplies.  If
    153  *  a function which you would not think utilize the FP unit DOES,
    154  *  then one can not easily predict which tasks will use the FP hardware.
    155  *  In this case, this option should be TRUE.
    156149 *
    157150 *  If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well.
  • cpukit/score/cpu/unix/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/unix/rtems/score/cpu.h

    rd956ef7 r3b1c100  
    11/*  cpu.h
    22 *
    3  *  This include file contains information pertaining to the HP
    4  *  PA-RISC processor (Level 1.1).
     3 *  This include file contains information pertaining to the
     4 *  UNIX port of RTEMS.
    55 *
    66 *  COPYRIGHT (c) 1994 by Division Incorporated
     
    164164 *  If TRUE, then the RTEMS_FLOATING_POINT task attribute is assumed.
    165165 *  If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
    166  *
    167  *  So far, the only CPU in which this option has been used is the
    168  *  HP PA-RISC.  The HP C compiler and gcc both implicitly use the
    169  *  floating point registers to perform integer multiplies.  If
    170  *  a function which you would not think utilize the FP unit DOES,
    171  *  then one can not easily predict which tasks will use the FP hardware.
    172  *  In this case, this option should be TRUE.
    173166 *
    174167 *  If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well.
Note: See TracChangeset for help on using the changeset viewer.