[M3commit] [modula3/cm3] 49df75: Add expected build output files to test p265.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/modula3/cm3
  Commit: 49df75611199c8cf3a965045ee65b76d0da15c1d
      https://github.com/modula3/cm3/commit/49df75611199c8cf3a965045ee65b76d0da15c1d
  Author: Rodney Bates <rodney.m.bates at acm.org>
  Date:   2017-08-12 (Sat, 12 Aug 2017)

  Changed paths:
    A m3-sys/m3tests/src/p2/p265/stderr.build
    A m3-sys/m3tests/src/p2/p265/stdout.build

  Log Message:
  -----------
  Add expected build output files to test p265.

This still detects compile time errors, which may be correct, but
if so, this should be an e group test.


  Commit: 90dedf2d1a91a5c37e739ce10e39016bb4e4f4f3
      https://github.com/modula3/cm3/commit/90dedf2d1a91a5c37e739ce10e39016bb4e4f4f3
  Author: Rodney Bates <rodney.m.bates at acm.org>
  Date:   2017-08-12 (Sat, 12 Aug 2017)

  Changed paths:
    A m3-sys/m3tests/src/p0/p004/README

  Log Message:
  -----------
  Add a README file to test p004, explaining different warning order.

The m3cc and llvm versions of the compiler produce the same set of
warning messages but in a different order.  This is probably because
these back ends request different order of nested procedures from
the front end.  Little else would affect the front end.

This test has no explicitly coded nested procedures, but exception
handling generates internally produced nested procedures.

The added README file just explains this.

Probably the difference in compile output could be checked automatically,
but it's a priority thing.


Compare: https://github.com/modula3/cm3/compare/ce560936a064...90dedf2d1a91