[M3commit] [modula3/cm3] 510651: Fix comment character here too -- more to do.

GitHub noreply at github.com
Fri Jul 1 03:43:40 CEST 2016

  Branch: refs/heads/master
  Home:   https://github.com/modula3/cm3
  Commit: 5106518ed2ea392d1ec28f475be77aebefcd34e3
  Author: jaykrell <jay.krell at cornell.edu>
  Date:   2016-06-26 (Sun, 26 Jun 2016)

  Changed paths:
    M m3-sys/cminstall/src/config-no-install/FreeBSD-old.common

  Log Message:
  Fix comment character here too -- more to do.

  Commit: a7133100ffa8fb2e15737a11fdc0c1fc87a783a9
  Author: jaykrell <jay.krell at cornell.edu>
  Date:   2016-06-26 (Sun, 26 Jun 2016)

  Changed paths:
    M m3-sys/cminstall/src/config-no-install/FreeBSD.common
    M m3-sys/cminstall/src/config-no-install/I386_FREEBSD.common

  Log Message:
  More I386_FREEBSD repair.
Perhaps we should drop pre-7.0 support, or, again, something more structured
or autoconf -- we want to use -m32 if supported, and -z now if supported.
They have both been around a while, and there are systems within memory that didn't have them.

  Commit: 58cab3d581488f78b638a1da9d4698fe07a6cbc7
  Author: jaykrell <jay.krell at cornell.edu>
  Date:   2016-06-26 (Sun, 26 Jun 2016)

  Changed paths:
    M m3-libs/m3core/src/thread/PTHREAD/m3makefile

  Log Message:
  With cm3 -boot at least, compile "all" the .c files:

They each contain #ifdef's in them such that they are empty
when they aren't meant to be used -- except they have "dummy" symbols
to avoid any warnings about being empty.

We could always compile them for all targets, it'd just be *slightly* slower
to build here.

The point here is to show that the target-specific C-based bootstraps
are all identical, modulo win32 vs. posix, 32bit vs. 64bit, little vs.
big endian, so that we can have, say, 6 targets total (until
such time as layout fed to the C backend is symbolc either
using struct member references or adding in sizeof(size_t) to
compute the offset -- then 32bit and 64bit become folded).

There is a slight target specificity otherwise in that different
targets contain these different .c files.

  Commit: b62ea16d571dca6b6c40c8bbeabf42c25f8bd86a
  Author: jaykrell <jay.krell at cornell.edu>
  Date:   2016-06-30 (Thu, 30 Jun 2016)

  Changed paths:
    M m3-sys/m3cc/gcc/gcc/m3cg/parse.c

  Log Message:
  Put spaces after quotes to head off possible C++-14 incompatibility -- really seen in real code
with current Visual C++ -- "foo"foo vs. "foo" foo, the thing right after the quote
makes it a literal to a constructor for a user defined type, so that more than just arrays of characters
can partake in this syntax.

Compare: https://github.com/modula3/cm3/compare/a3ada5c742e2...b62ea16d571d

More information about the M3commit mailing list