Bytes stored in target order, not host order.

diff --git a/gprof/ChangeLog b/gprof/ChangeLog
index e6772f3..a57e13d 100644 (file)
--- a/gprof/ChangeLog
+++ b/gprof/ChangeLog
@@ -1,3 +1,8 @@
+2001-06-12  Ben Elliston  <bje@redhat.com>
+
+       * gprof.texi (File Format): Profile data files are stored in
+       target byte order, not host byte order.
+
 2001-05-16  Alexandre Oliva  <aoliva@redhat.com>
 
        * gmon_io.c (gmon_io_read, gmon_io_write_vma,

diff --git a/gprof/gprof.texi b/gprof/gprof.texi
index 2008da7..b7e3388 100644 (file)
--- a/gprof/gprof.texi
+++ b/gprof/gprof.texi
@@ -1836,9 +1836,9 @@ format.
 The new file format is defined in header file @file{gmon_out.h}.  It
 consists of a header containing the magic cookie and a version number,
 as well as some spare bytes available for future extensions.  All data
-in a profile data file is in the native format of the host on which
-the profile was collected.  @sc{gnu} @code{gprof} adapts automatically to the
-byte-order in use.
+in a profile data file is in the native format of the target for which
+the profile was collected.  @sc{gnu} @code{gprof} adapts automatically
+to the byte-order in use.
 
 In the new file format, the header is followed by a sequence of
 records.  Currently, there are three different record types: histogram