summaryrefslogtreecommitdiff
path: root/gcc/rtl.texi
diff options
context:
space:
mode:
authoramylaar <amylaar@138bc75d-0d04-0410-961f-82ee72b054a4>1997-12-03 23:37:38 +0000
committeramylaar <amylaar@138bc75d-0d04-0410-961f-82ee72b054a4>1997-12-03 23:37:38 +0000
commit03ccabb4735803c207ab20796e8c5b15e125222f (patch)
tree85697d69e24ffe6b1992e2b6937bfdb40f7fc754 /gcc/rtl.texi
parent2a78847c33ac6a912ae280da4d4383f035e86139 (diff)
downloadgcc-03ccabb4735803c207ab20796e8c5b15e125222f.tar.gz
Added some words on FLOAT_WORDS_BIG_ENDIAN.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@16932 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/rtl.texi')
-rw-r--r--gcc/rtl.texi9
1 files changed, 9 insertions, 0 deletions
diff --git a/gcc/rtl.texi b/gcc/rtl.texi
index 3a4de0c67c1..c8d51d121e1 100644
--- a/gcc/rtl.texi
+++ b/gcc/rtl.texi
@@ -1096,6 +1096,15 @@ The compilation parameter @code{WORDS_BIG_ENDIAN}, if set to 1, says
that word number zero is the most significant part; otherwise, it is
the least significant part.
+@cindex @code{FLOAT_WORDS_BIG_ENDIAN}, (lack of) effect on @code{subreg}
+On a few targets, @code{FLOAT_WORDS_BIG_ENDIAN} disagrees with
+@code{WORDS_BIG_ENDIAN}.
+However, most parts of the compiler treat floating point values as if
+they had the same endianness as integer values. This works because
+they handle them solely as a collection of integer values, with no
+particular numerical value. Only real.c and the runtime libraries
+care about @code{FLOAT_WORDS_BIG_ENDIAN}.
+
@cindex combiner pass
@cindex reload pass
@cindex @code{subreg}, special reload handling