gcc/libgcobol
GCC Administrator 890dff609d Daily bump. 2025-11-14 00:20:34 +00:00
..
compat cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
posix cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
.gitignore cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
ChangeLog Daily bump. 2025-11-14 00:20:34 +00:00
LICENSE libgcobol: Add license. 2025-06-20 10:18:37 -04:00
Makefile.am cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
Makefile.in cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
README
acinclude.m4 libgcobol: Handle long double as an alternate IEEE754 quad [PR119244] 2025-04-15 07:55:55 +02:00
aclocal.m4 *: regenerate autotools 2025-10-05 17:14:49 +01:00
charmaps.cc cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
charmaps.h cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
common-defs.h cobol: Implement the XML PARSE statement. 2025-10-23 11:28:53 -04:00
config.h.in cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
configure cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
configure.ac cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
configure.tgt libgcobol: mark riscv64-*-linux* as supported target 2025-04-15 16:59:03 +02:00
constants.cc cobol: Implement the XML PARSE statement. 2025-10-23 11:28:53 -04:00
ec.h cobol: Multiple PRs; formatting; exception processing. 2025-05-20 14:24:30 -04:00
encodings.h cobol: Mainly extends compilation and execution in finternal-ebcdic. 2025-11-06 08:57:54 -05:00
exceptl.h cobol: Rewrite exception handling. Partially refactor subscript/refmod calculations. 2025-05-04 21:38:57 -04:00
gcobolio.h cobol: Mainly extends compilation and execution in finternal-ebcdic. 2025-11-06 08:57:54 -05:00
gfileio.cc cobol: Mainly extends compilation and execution in finternal-ebcdic. 2025-11-06 08:57:54 -05:00
gfileio.h cobol: Confine all __int128/_Float128 references to libgcobol. 2025-03-28 12:21:05 -04:00
gmath.cc cobol: Eliminate cppcheck warnings for libgcobol [PR119323] 2025-06-04 11:31:51 -04:00
gmath.h
intrinsic.cc cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
io.cc cobol: Multiple PRs; formatting; exception processing. 2025-05-20 14:24:30 -04:00
io.h
libgcobol-fp.h libgcobol: Handle long double as an alternate IEEE754 quad [PR119244] 2025-04-15 07:55:55 +02:00
libgcobol.cc cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
libgcobol.h cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
libgcobol.spec.in libgcobol: Allow libgcobol to use libquadmath [PR119244]. 2025-04-10 11:05:07 +01:00
stringbin.cc cobol: Convert to individual variable character-set encoding. 2025-10-10 13:19:34 -04:00
stringbin.h cobol: Convert to individual variable character-set encoding. 2025-10-10 13:19:34 -04:00
valconv.cc cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00
valconv.h cobol: Convert to individual variable character-set encoding. 2025-10-10 13:19:34 -04:00
xmlparse.cc cobol: Introduce vendor-compatibility layer as user-defined functions. 2025-11-12 19:49:39 -05:00

README

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.