[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Commits] r16979 - in /libdfp/trunk: ChangeLog Makefile.in README.developer README.maintainer README.user



Author: ryanarn
Date: Sat Feb  4 18:37:44 2012
New Revision: 16979

Log:
Added discussion of __STDC_DEC_FP__ to README.user and added install-readme
rule which installs README.user as "README" in docdir/dfp/.

2012-02-04  Ryan S. Arnold  <rsa@xxxxxxxxxxxxxxxxxx>

	* Makefile.in (install-readme): New target.
	(install): Consolidated by making install-headers and install-readme
	as dependent rules.
	* README.maintainer: Updated info on Versioning.
	* README.user: Added discussion on __STDC_DEC_FP__
	* README.developer: Updated info on Versioning.

Modified:
    libdfp/trunk/ChangeLog
    libdfp/trunk/Makefile.in
    libdfp/trunk/README.developer
    libdfp/trunk/README.maintainer
    libdfp/trunk/README.user

Modified: libdfp/trunk/ChangeLog
==============================================================================
--- libdfp/trunk/ChangeLog (original)
+++ libdfp/trunk/ChangeLog Sat Feb  4 18:37:44 2012
@@ -1,3 +1,12 @@
+2012-02-04  Ryan S. Arnold  <rsa@xxxxxxxxxxxxxxxxxx>
+
+	* Makefile.in (install-readme): New target.
+	(install): Consolidated by making install-headers and install-readme
+	as dependent rules.
+	* README.maintainer: Updated info on Versioning.
+	* README.user: Added discussion on __STDC_DEC_FP__
+	* README.developer: Updated info on Versioning.
+
 2012-01-17  Ryan S. Arnold  <rsa@xxxxxxxxxxxxxxxxxx>
 
 	* sysdeps/powerpc/powerpc32/power6x/Implies: Points to power6.

Modified: libdfp/trunk/Makefile.in
==============================================================================
--- libdfp/trunk/Makefile.in (original)
+++ libdfp/trunk/Makefile.in Sat Feb  4 18:37:44 2012
@@ -9,6 +9,7 @@
 exec_prefix = @exec_prefix@
 libdir = @libdir@
 includedir = @includedir@
+docdir =
 
 # Where to install the library and object files.
 ifndef libdir
@@ -21,6 +22,12 @@
 includedir = $(prefix)/include
 endif
 inst_includedir = $(install_root)$(includedir)
+
+# Where to install the README document
+ifndef docdir
+docdir = $(prefix)/share/doc/
+endif
+inst_docdir = $(install_root)$(docdir)
 
 dfp_name = @PACKAGE_NAME@
 dfp_version = @PACKAGE_VERSION@
@@ -396,7 +403,7 @@
 
 .PHONY: clean
 
-install: all
+install: all install-readme install-headers
 	$(INSTALL) -d $(inst_libdir)
 ifeq ("@enable_static@","static")
 	$(INSTALL) -t $(inst_libdir) $(top_builddir)/$(STATIC_LIB)
@@ -404,11 +411,14 @@
 	$(INSTALL) -t $(inst_libdir) $(top_builddir)/$(SHARED_REALNAME_LIB)
 	ln -f -s $(SHARED_REALNAME_LIB) $(inst_libdir)/$(SHARED_LINKERNAME_LIB)
 	$(LDCONFIG) -l $(inst_libdir)/$(SHARED_REALNAME_LIB)
-	$(INSTALL) -d $(inst_includedir)
-	$(INSTALL) -d $(inst_includedir)/dfp
-	$(INSTALL) -d $(inst_includedir)/dfp/decimal
-	$(INSTALL) -t $(inst_includedir)/dfp $(top_srcdir)/dfp/*.h
-	$(INSTALL) -t $(inst_includedir)/dfp/decimal/ $(top_srcdir)/dfp/decimal/*
+#	$(INSTALL) -d $(inst_includedir)
+#	$(INSTALL) -d $(inst_includedir)/dfp
+#	$(INSTALL) -d $(inst_includedir)/dfp/decimal
+#	$(INSTALL) -t $(inst_includedir)/dfp $(top_srcdir)/dfp/*.h
+#	$(INSTALL) -t $(inst_includedir)/dfp/decimal/ $(top_srcdir)/dfp/decimal/*
+#	#$(INSTALL) -d $(inst_docdir)dfp/
+#	#$(INSTALL) -t $(inst_docdir)dfp/ $(top_srcdir)/README.user
+#	#mv $(inst_docdir)dfp/README.user $(inst_docdir)dfp/README
 .PHONY: install
 
 install-headers:
@@ -419,6 +429,12 @@
 	$(INSTALL) -t $(inst_includedir)/dfp/decimal/ $(top_srcdir)/dfp/decimal/*
 .PHONY: install-headers
 
+install-readme:
+	$(INSTALL) -d $(inst_docdir)dfp/
+	$(INSTALL) -t $(inst_docdir)dfp/ $(top_srcdir)/README.user
+	mv $(inst_docdir)dfp/README.user $(inst_docdir)dfp/README
+.PHONY: install-readme
+
 # Clean out the existing .SUFFIXES setting.
 .SUFFIXES:
 # Prioritize .S over .c when searching for target files.  The .os suffix

Modified: libdfp/trunk/README.developer
==============================================================================
--- libdfp/trunk/README.developer (original)
+++ libdfp/trunk/README.developer Sat Feb  4 18:37:44 2012
@@ -37,6 +37,7 @@
 	  5.1  Configure Switches
 	6.  Source Tree Layout
 	7.  Make Rules
+	8.  Adding New Functions (API changes) (TODO)
 	8.  Precision (TODO)
 	9.  Testing (make check) (TODO)
 	10. Contribution Checklist (TODO)
@@ -646,6 +647,19 @@
 
 [TODO] make distclean
 
+
+---------------------------------------------------------------------------
+8.  Adding New Functions (API changes) (TODO)
+
+Libdfp versioning uses the following convention:
+
+	major.minor.revision
+
+New functions must ALWAYS be added to the next revision number of the library.
+For instance, if the maintainer has designated the current release at 1.0.8
+new function should be added to 1.0.9.  Then, when the maintainer increments
+the library to 1.0.9 the new functions will become available.
+
 ---------------------------------------------------------------------------
 Appendices
 ---------------------------------------------------------------------------

Modified: libdfp/trunk/README.maintainer
==============================================================================
--- libdfp/trunk/README.maintainer (original)
+++ libdfp/trunk/README.maintainer Sat Feb  4 18:37:44 2012
@@ -20,15 +20,23 @@
 	2.  Specification
 	  2.1  DFP Spec
 	  2.2  Spec Changes
-	3.  DFP ABI Changes
-	4.  Versioning
-	5.  Mailing Lists
-	6.  ChangeLog
-	7.  Backends
-	8.  Bugs
-	9.  Contributions
-	10. Commit Access
+	3.  Libdfp API Changes
+	4.  Libdfp ABI Changes
+	5.  Versioning
+	6.  Mailing Lists
+	7.  ChangeLog
+	8.  Backends
+	9.  Bugs
+	10.  Contributions
+	11. Commit Access
 
+
+---------------------------------------------------------------------------
+3.  Libdfp API Changes
+
+When new functions or interfaces are added to Libdfp then the API has changed
+and the library version must change.  For guidelines on adding new symbols to
+a particular version see README.developer.
 
 ---------------------------------------------------------------------------
 10.  Commit Access

Modified: libdfp/trunk/README.user
==============================================================================
--- libdfp/trunk/README.user (original)
+++ libdfp/trunk/README.user Sat Feb  4 18:37:44 2012
@@ -23,11 +23,12 @@
 	  1.3.  Backends (libdecnumber & libbid)
 	2.  Availability
 	3.  Compliance With ISO/IEC TR 24732
-	  3.1  __STDC_WANT_DEC_FP__
-	  3.2  GNU99 Compatibility
-	  3.3  scanf Support
-	  3.4  printf Support
-	    3.4.1 printf "a,A" Conversion Specifier
+	  3.1  __STDC_DEC_FP__
+	  3.2  __STDC_WANT_DEC_FP__
+	  3.3  GNU99 Compatibility
+	  3.4  scanf Support
+	  3.5  printf Support
+	    3.5.1 printf "a,A" Conversion Specifier
 	4.  Dependencies
 	  4.1  GNU/Linux OS
 	  4.2  GLIBC Minimum Version
@@ -103,7 +104,38 @@
 This section covers issues related to compliance with ISO/IEC TR 24732.
 
 ---------------------------------------------------------------------------
-3.1 __STDC_WANT_DEC_FP__
+3.1 __STDC_DEC_FP__
+
+The draft standard ISO/IEC TR 24732 specifies the macro __STDC_DEC_FP__ as
+integer constant 200805L to indicate conformance to the technical report.
+
+This macro describes properties of the compiler and library that together
+satisfy the technical report.
+
+The intention is that user applications may check for conformance with the
+following:
+
+#ifdef __STDC_DEC_FP__
+/* Select implementation conforming to the TR.  */
+#else
+/* Select non-conforming DFP emulation library.  */
+#endif
+
+Since __STDC_DEC_FP__ is a property fulfilled by both the compiler and
+library the compiler can't predefine this macro without know if the user is
+using libdfp.  There is currently no mechanism for the compiler to
+determine this early in the translation unit.
+
+This will eventually be provided, once a mechanism is added into GLIBC and
+GCC for identifying stdc predefines as highlighted in this email:
+
+http://sourceware.org/ml/libc-alpha/2009-04/msg00005.html
+
+At that point libdfp will provide __STDC_DEC_FP__ for GLIBC versions
+greater than FOO and GCC versions greater than BAR.
+
+---------------------------------------------------------------------------
+3.2 __STDC_WANT_DEC_FP__
 
 The standard ISO/IEC TR 24732 indicates that programs that wish to use
 Decimal Floating Point should define the following macro:
@@ -121,7 +153,7 @@
 up the DFP function prototypes and data types defined in these headers.
 
 ---------------------------------------------------------------------------
-3.2 GNU99 Compatibility
+3.3 GNU99 Compatibility
 
 GNU99 compatibility is required to pick up some DFP prototypes that are
 similar to the binary floating point prototypes guarded in <math.h> by
@@ -140,7 +172,7 @@
 Compile with -Wall to pick up undefined prototype warnings.
 
 ---------------------------------------------------------------------------
-3.3 scanf Support
+3.4 scanf Support
 
 Libdfp does not, and will not comply with the TR 24732 requirement for the
 addition of scanf in support of decimal floating point data types.  The
@@ -148,7 +180,7 @@
 implications of scanf.
 
 ---------------------------------------------------------------------------
-3.4 printf Support
+3.5 printf Support
 
 Libdfp supports the addition of the printf format codes indicated by TR
 24732.  GLIBC proper owns the printf implementation.  Libdfp utilizes the
@@ -178,7 +210,7 @@
 Therefore, any combination of DFP length modifiers and spec characters is
 supported.
 
-3.4.1 printf "a,A" Conversion Specifier
+3.5.1 printf "a,A" Conversion Specifier
 ---------------------------------------------------------------------------
 
 The ISO-C DFP specification adds "a/A" as a printf conversion specifier.

_______________________________________________
Commits mailing list
Commits@xxxxxxxxxx
http://eglibc.org/cgi-bin/mailman/listinfo/commits