summaryrefslogtreecommitdiffstats
path: root/cpukit/score/cpu/h8300/rtems/score/cpu.h
diff options
context:
space:
mode:
Diffstat (limited to 'cpukit/score/cpu/h8300/rtems/score/cpu.h')
-rw-r--r--cpukit/score/cpu/h8300/rtems/score/cpu.h7
1 files changed, 0 insertions, 7 deletions
diff --git a/cpukit/score/cpu/h8300/rtems/score/cpu.h b/cpukit/score/cpu/h8300/rtems/score/cpu.h
index 98d790bfc6..d7abc15b5f 100644
--- a/cpukit/score/cpu/h8300/rtems/score/cpu.h
+++ b/cpukit/score/cpu/h8300/rtems/score/cpu.h
@@ -171,13 +171,6 @@ extern "C" {
* If TRUE, then the RTEMS_FLOATING_POINT task attribute is assumed.
* If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
*
- * So far, the only CPU in which this option has been used is the
- * HP PA-RISC. The HP C compiler and gcc both implicitly use the
- * floating point registers to perform integer multiplies. If
- * a function which you would not think utilize the FP unit DOES,
- * then one can not easily predict which tasks will use the FP hardware.
- * In this case, this option should be TRUE.
- *
* If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well.
*
* H8300 Specific Information: