Skip to content

Releases

oo2c 2.2.4

Choose a tag to compare

@tkurtbond tkurtbond released this 17 Nov 17:37
v2.2.4

A bug fix release: oo2c built with --enable-threads=pthreads now
links on FreeBSD.

  • With --enable-threads=pthreads, configure uses -lgc-threaded when
    -lgc has no thread support (GC_pthread_create). This is the case
    on FreeBSD, where boehm-gc-threaded provides the threaded gc
    (pkg install boehm-gc-threaded). Threads now work on FreeBSD,
    OpenBSD and NetBSD.

oo2c 2.2.3

Choose a tag to compare

@tkurtbond tkurtbond released this 17 Nov 14:12
v2.2.3

The first release with a tarball for 32-bit systems, oo2c_32, next
to oo2c_64. Tested by the CI on x86-64, aarch64 and i386 Linux and
on FreeBSD, OpenBSD and NetBSD. The compiler and the library build
and pass make test with no gcc warnings.

  • POINTER [CSTRING] TO ARRAY OF CHAR implies NO_LENGTH_INFO for the
    array. Such a pointer can refer to a string constant or any
    character array, which has no length information, so LEN(p^) read
    memory before the string. LEN(p^) and passing p^ to an open-array
    parameter are now compile-time errors; walk the string to its 0X
    instead.
  • make test-valgrind and make test-asan run the tests/ssa and
    tests/lib test programs under valgrind memcheck, or compiled with
    AddressSanitizer and UndefinedBehaviorSanitizer. Fixed the
    undefined behaviour they found in ASH, SYSTEM.ROT, empty open-array
    value parameters and the HashCode hash functions.
  • "make dist32" makes the oo2c_32 tarball (for systems with 4-byte
    pointers) on a 64-bit system, and releases now include it. The
    old "make dist64" target did not work with current autoconf.
  • Open-array parameters are declared in the generated C as pointers
    (T *a) instead of arrays (T a[]). This is the same type in C, but
    for T a[] gcc assumed at least one element and gave false
    -Wstringop-overread/-overflow warnings, e.g. for an empty array.
  • The oocdoc HTML pages no longer list Object twice under "Import
    List" when a module imports it under another name.

oo2c 2.2.2

Choose a tag to compare

@tkurtbond tkurtbond released this 17 Nov 02:49
v2.2.2

Builds on FreeBSD, OpenBSD and NetBSD. Tested on FreeBSD 15.1
(x86-64 and aarch64), OpenBSD 7.9 and NetBSD 11.0 and 11.1, and on
aarch64 Linux; see INSTALL for the packages and configure settings.

  • The Makefile runs oo2c through the shell. On NetBSD 11.0, GNU make
    started it with posix_spawn, and a kernel bug (PR kern/60653, fixed
    in 11.1) then made the garbage collector crash at random in GC_init.
  • The hand-written C uses snprintf, vsnprintf and memcpy instead of
    sprintf, vsprintf and strcpy, which OpenBSD's linker warns about.
    The library module libc has snprintf instead of sprintf.
  • CI on GitHub also builds and tests on aarch64 Linux and in FreeBSD,
    OpenBSD and NetBSD VMs.

oo2c 2.2.1

Choose a tag to compare

@tkurtbond tkurtbond released this 16 Nov 19:52
v2.2.1

Fixes the build on Debian and Ubuntu. Tested on Fedora 44 and 45 with
gcc 16, and on Ubuntu 26.04 with gcc 15.

  • Programs are linked with the libraries of the run-time system (-lm,
    -lgc, ...) even when liboo2c is a shared library. Generated C calls
    libm directly, and on Debian and Ubuntu, whose libtool and linker do
    not pass on a shared library's dependencies, the 2.2.0 tarball
    failed to link bin/oo2c ("DSO missing from command line").
  • CI on GitHub: build, self-host and test on current Fedora and Ubuntu
    (.github/ci-build.sh).

oo2c 2.2.0

Choose a tag to compare

@tkurtbond tkurtbond released this 16 Nov 18:04
v2.2.0

Release notes for the modern-linux fork of OOC (oo2c)

Bug reports: https://github.com/tkurtbond/oo2c/issues

oo2c 2.2.0

The first release of this fork, based on OOC 2.1.11 (the last upstream
release; development stopped around 2011). It builds and runs on
current Linux: tested on Fedora 44 with gcc 16, glibc 2.4x, Boehm gc
8.2, libtool 2.5 and autoconf 2.72. The release tarball
oo2c_64-2.2.0.tar.bz2 bootstraps on a 64-bit system with no oo2c
installed.

Language and compiler changes:

  • Using a local (nested) procedure as a procedure value is now an
    error (error 81), as the Oberon-2 report requires. The generated C
    would have needed an executable stack. Programs that did this and
    compiled with 2.1.11 must be changed.
  • Array types with a negative length are rejected.
  • A type guard is allowed on the target of an assignment.
  • ARRAY OF BYTE parameters get the byte size of an open array
    argument, not its element count.
  • The optimizer folds comparisons of a non-real value with itself
    (x=x, x<x, ...).

Generated C and build:

  • Generated C compiles with gcc 16 without warnings: program main
    files declare OOC__open, libc functions taking char* are
    called through C wrappers, and every generated file silences gcc's
    -Wunused-label, -Wunused-but-set-variable and -Wunused-parameter.
  • configure adds -fno-strict-aliasing for gcc, which applies to every
    program oo2c compiles.
  • libtool is called with --tag=CC instead of --tag=CXX, so -lm is not
    dropped from liboo2c.la with libtool 2.x.
  • With --enable-threads=pthreads, GC_THREADS is defined for Boehm gc 7
    and later, so thread stacks are scanned.
  • configure.ac and aclocal.m4 are updated for autoconf 2.72.
  • Runtime C files and hand-written library C are fixed for -Wall
    -Wextra and deprecated APIs.
  • make dist works again and names the tarball after the pointer size
    (oo2c_32 or oo2c_64).

Tests:

  • The 64-bit reference C output of tests/ssa-c-output is in git, stale
    test data is fixed, and the hostess test cases run with the v2 test
    framework (make test-hostess-ooc1).

The shared library is still liboo2c.so.3.