[all-commits] [llvm/llvm-project] aa03fb: [libcxx] [test] Add a test parameter for disabling...

[Nikita Popov via All-commits]

  Branch: refs/heads/release/17.x
  Home:   https://github.com/llvm/llvm-project
  Commit: aa03fba83b17bbfcd9ed869efed2818b503875d6
      https://github.com/llvm/llvm-project/commit/aa03fba83b17bbfcd9ed869efed2818b503875d6
  Author: Martin Storsjö <martin at martin.st>
  Date:   2023-10-24 (Tue, 24 Oct 2023)

  Changed paths:
    M libcxx/test/std/input.output/string.streams/stringstream/stringstream.members/gcount.pass.cpp
    M libcxx/utils/libcxx/test/params.py

  Log Message:
  -----------
  [libcxx] [test] Add a test parameter for disabling memory intensive tests (#68214)

Specifically, the test std/input.output/string.streams/stringstream/stringstream.members/gcount.pass.cpp
allocates a std::string with INT_MAX-1 elements, and then writes this to
a std::stringstream. On Linux, running this test consumes around 5.0 GB
of memory; on Windows, it ends up using up to 6.8 GB of memory.

This limits whether such tests can run on e.g. GitHub Actions runners,
where the free runners are limited to 8 GB of memory.

This is somewhat similar to, but still notably different, from the
existing test parameter long_tests.

(cherry picked from commit 122064a6303eb9c06e0af231f5a4ce145d9a2e67)


  Commit: a7101379d75e9a3d9a3d9bf32c10ae01f909209a
      https://github.com/llvm/llvm-project/commit/a7101379d75e9a3d9a3d9bf32c10ae01f909209a
  Author: DianQK <dianqk at dianqk.net>
  Date:   2023-10-24 (Tue, 24 Oct 2023)

  Changed paths:
    M llvm/lib/Transforms/Scalar/CorrelatedValuePropagation.cpp
    M llvm/test/Transforms/CorrelatedValuePropagation/abs.ll

  Log Message:
  -----------
  [LVI][CVP] Treat undef like a full range on abs(x, false) (#68711)

Fixes #68682.

(cherry picked from commit 2ad9a658005e6a4204d7ee617c3949632a707aa5)


  Commit: ef50a367e3d5ceaff7468d804987516a4520e9ac
      https://github.com/llvm/llvm-project/commit/ef50a367e3d5ceaff7468d804987516a4520e9ac
  Author: Brad Smith <brad at comstyle.com>
  Date:   2023-10-24 (Tue, 24 Oct 2023)

  Changed paths:
    M mlir/lib/ExecutionEngine/CRunnerUtils.cpp

  Log Message:
  -----------
  [mlir] Avoid including <alloca.h> on DragonFly

(cherry picked from commit a157a82b1e7a8d4be34cc862db4b42fa9db363d0)


  Commit: a1c67ffd0a1f85f283f1ec734827c6306031bafb
      https://github.com/llvm/llvm-project/commit/a1c67ffd0a1f85f283f1ec734827c6306031bafb
  Author: Nikita Popov <npopov at redhat.com>
  Date:   2023-10-24 (Tue, 24 Oct 2023)

  Changed paths:
    M llvm/test/Transforms/ConstraintElimination/large-constant-ints.ll

  Log Message:
  -----------
  [ConstraintElim] Add test for #68751 (NFC)

(cherry picked from commit 2b74db6c9bff757ce016d62a7086617e2b9e43b3)


  Commit: 7f790f9a39e3178957ca965e97503eeda4c5ce23
      https://github.com/llvm/llvm-project/commit/7f790f9a39e3178957ca965e97503eeda4c5ce23
  Author: Nikita Popov <npopov at redhat.com>
  Date:   2023-10-24 (Tue, 24 Oct 2023)

  Changed paths:
    M llvm/lib/Transforms/Scalar/ConstraintElimination.cpp
    M llvm/test/Transforms/ConstraintElimination/large-constant-ints.ll
    M llvm/test/Transforms/ConstraintElimination/shl.ll

  Log Message:
  -----------
  [ConstraintElim] Don't decompose values wider than 64 bits (#68803)

Our coefficients are 64-bits, so adding/multiplying them can wrap in
64-bits even if there would be no wrapping the full bit width.

The alternative would be to check for overflows during all adds/muls in
decomposition. I assume that we don't particularly care about handling
wide integers here, so I've opted to bail out.

Fixes https://github.com/llvm/llvm-project/issues/68751.

(cherry picked from commit 1d43096e16ff7288c7feac1ae81fd4f745ce10bb)


Compare: https://github.com/llvm/llvm-project/compare/71f408bc3623...7f790f9a39e3