summaryrefslogtreecommitdiffstats
path: root/windows/src/H5Tinit.c
diff options
context:
space:
mode:
authorFang Guo <fangguo@ncsa.uiuc.edu>2005-03-31 18:53:02 (GMT)
committerFang Guo <fangguo@ncsa.uiuc.edu>2005-03-31 18:53:02 (GMT)
commit60ad9bc65c994da12f2e35ef89e7839c32c9abbd (patch)
treef3113f8fc0f4150c7d276b30beb267482eb5e623 /windows/src/H5Tinit.c
parent0a97c546d512a6943f93a8b07fa37aad1802be69 (diff)
downloadhdf5-60ad9bc65c994da12f2e35ef89e7839c32c9abbd.zip
hdf5-60ad9bc65c994da12f2e35ef89e7839c32c9abbd.tar.gz
hdf5-60ad9bc65c994da12f2e35ef89e7839c32c9abbd.tar.bz2
[svn-r10521] Purpose:
Update windows misc file. Description: Solution: Platforms tested: Misc. update:
Diffstat (limited to 'windows/src/H5Tinit.c')
-rwxr-xr-xwindows/src/H5Tinit.c90
1 files changed, 45 insertions, 45 deletions
diff --git a/windows/src/H5Tinit.c b/windows/src/H5Tinit.c
index 3f82043..e06ead1 100755
--- a/windows/src/H5Tinit.c
+++ b/windows/src/H5Tinit.c
@@ -16,50 +16,50 @@
* access to either file, you may request a copy from hdfhelp@ncsa.uiuc.edu. *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
- * Created: Jan 24, 2005
- *
+ * Created: Mar 30, 2005
+ *
*
- * Purpose: This machine-generated source code contains
- * information about the various integer and
- * floating point numeric formats found on this
- * architecture. The parameters below should be
- * checked carefully and errors reported to the
- * HDF5 maintainer.
- *
- * Each of the numeric formats listed below are
- * printed from most significant bit to least
- * significant bit even though the actual bytes
- * might be stored in a different order in
- * memory. The integers above each binary byte
- * indicate the relative order of the bytes in
- * memory; little-endian machines have
- * decreasing numbers while big-endian machines
- * have increasing numbers.
- *
- * The fields of the numbers are printed as
- * letters with `S' for the mantissa sign bit,
- * `M' for the mantissa magnitude, and `E' for
- * the exponent. The exponent has an associated
- * bias which can be subtracted to find the
- * true exponent. The radix point is assumed
- * to be before the first `M' bit. Any bit
- * of a floating-point value not falling into one
- * of these categories is printed as a question
- * mark. Bits of integer types are printed as
- * `I' for 2's complement and `U' for magnitude.
- *
- * If the most significant bit of the normalized
- * mantissa (always a `1' except for `0.0') is
- * not stored then an `implicit=yes' appears
- * under the field description. In thie case,
- * the radix point is still assumed to be
- * before the first `M' but after the implicit
- * bit.
+ * Purpose: This machine-generated source code contains
+ * information about the various integer and
+ * floating point numeric formats found on this
+ * architecture. The parameters below should be
+ * checked carefully and errors reported to the
+ * HDF5 maintainer.
+ *
+ * Each of the numeric formats listed below are
+ * printed from most significant bit to least
+ * significant bit even though the actual bytes
+ * might be stored in a different order in
+ * memory. The integers above each binary byte
+ * indicate the relative order of the bytes in
+ * memory; little-endian machines have
+ * decreasing numbers while big-endian machines
+ * have increasing numbers.
+ *
+ * The fields of the numbers are printed as
+ * letters with `S' for the mantissa sign bit,
+ * `M' for the mantissa magnitude, and `E' for
+ * the exponent. The exponent has an associated
+ * bias which can be subtracted to find the
+ * true exponent. The radix point is assumed
+ * to be before the first `M' bit. Any bit
+ * of a floating-point value not falling into one
+ * of these categories is printed as a question
+ * mark. Bits of integer types are printed as
+ * `I' for 2's complement and `U' for magnitude.
+ *
+ * If the most significant bit of the normalized
+ * mantissa (always a `1' except for `0.0') is
+ * not stored then an `implicit=yes' appears
+ * under the field description. In thie case,
+ * the radix point is still assumed to be
+ * before the first `M' but after the implicit
+ * bit.
*
* Modifications:
*
- * DO NOT MAKE MODIFICATIONS TO THIS FILE!
- * It was generated by code in `H5detect.c'.
+ * DO NOT MAKE MODIFICATIONS TO THIS FILE!
+ * It was generated by code in `H5detect.c'.
*
*-------------------------------------------------------------------------
*/
@@ -81,14 +81,11 @@ H5FL_EXTERN(H5T_shared_t);
herr_t
H5TN_init_interface(void)
{
- H5T_t *dt = NULL;
- herr_t ret_value = SUCCEED;
+ H5T_t *dt = NULL;
+ herr_t ret_value = SUCCEED;
FUNC_ENTER_NOAPI(H5TN_init_interface, FAIL);
- /* Set the native order for this machine */
- H5T_native_order_g = H5T_ORDER_LE;
-
/*
* 0
* IIIIIIII
@@ -616,6 +613,9 @@ H5TN_init_interface(void)
H5T_NATIVE_LDOUBLE_ALIGN_g = 1;
H5T_NATIVE_LDOUBLE_COMP_ALIGN_g = 8;
+ /* Set the native order for this machine */
+ H5T_native_order_g = H5T_ORDER_LE;
+
/* Structure alignment for pointers, hvl_t, hobj_ref_t, hdset_reg_ref_t */
H5T_POINTER_COMP_ALIGN_g = 4;
H5T_HVL_COMP_ALIGN_g = 4;