95f10974a9
Many of the changes are mechanical: 1. 'GCOB_FP128' in place of _Float128. 2. Using FP128_FUNC to represent the spelling of intrinsics. 3. Using GCOB_FP128_LITERAL() to choose the suffix for literals. This allows for: __float128 and 'q' as the suffix when libquadmath is configured. _Float128 / 'f128' when IEC-60559 is available in libc long double / 'l' when long double is ieee753 128b. Add libquadmath to libgcobol.spec and its dependencies where the platform needs it. PR cobol/119244 libgcobol/ChangeLog: * Makefile.am: Add support for libquadmath. * Makefile.in: Regenerate. * acinclude.m4: Add support for libquadmath. * config.h.in: Regenerate. * configure: Regenerate. * configure.ac: Configure libquadmath support. * gmath.cc: Use GCOB_FP128 to represent the configured 128b floating point type. Use FP128_FUNC to represent the naming of intrinsics in the configure 128b floating point type. Render literals with GCOB_FP128_LITERAL. * intrinsic.cc: Likewise. * libgcobol.cc: Likewise. * libgcobol.h: Likewise. * libgcobol-fp.h: New file. * gfileio.cc: Include libgcobol-fp.h. * libgcobol.spec.in: Add libquadmath configure output. Signed-off-by: Iain Sandoe <iain@sandoe.co.uk> |
||
|---|---|---|
| .. | ||
| acinclude.m4 | ||
| aclocal.m4 | ||
| ChangeLog | ||
| charmaps.cc | ||
| charmaps.h | ||
| common-defs.h | ||
| config.h.in | ||
| configure | ||
| configure.ac | ||
| configure.tgt | ||
| constants.cc | ||
| ec.h | ||
| exceptl.h | ||
| gcobolio.h | ||
| gfileio.cc | ||
| gfileio.h | ||
| gmath.cc | ||
| gmath.h | ||
| intrinsic.cc | ||
| io.cc | ||
| io.h | ||
| libgcobol-fp.h | ||
| libgcobol.cc | ||
| libgcobol.h | ||
| libgcobol.spec.in | ||
| Makefile.am | ||
| Makefile.in | ||
| README | ||
| valconv.cc | ||
| valconv.h | ||
The libgcobol is intended for use entirely and solely by executables created from COBOL source code by the GCOBOL "COBOL for GCC" front end. libgcobol.a can be staticly linked in, but it makes for very large binaries. We tend to use that for debugging the GCOBOL compiler, and not much else Many of the functions in the library are called by the executable code generated by the GCOBOL compiler through GIMPLE tags, and thus prototypes -- which are part of the C/C++ programming paradigm -- are not used. Both the calling program and the called program use the extern "C" construction so that the linker can find the functions, and they need to agree ahead of time about the meaning of passed parameters.