Skip to content

Reject --enable-randomized-msgq on reconverse builds; manual points at +randomized_msgq - #4029

Merged
lvkale merged 2 commits into
reviewed-with-reconversefrom
reconverse-reject-randomized-msgq
Oct 12, 2026
Merged

lvkale merged 2 commits into
reviewed-with-reconversefrom
reconverse-reject-randomized-msgq

Conversation

@lvkale

@lvkale lvkale commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

--enable-randomized-msgq (CMake RANDOMIZED_MSGQ -> CMK_RANDOMIZED_MSGQ) only changes classic Converse's scheduler queue (src/conv-core/msgq.h), which reconverse builds do not compile, so on reconverse the option was accepted and did nothing. Reconverse now provides randomization as a run-time flag, +randomized_msgq with optional +randomized_seed <N> (charmplusplus/reconverse#269).

This PR makes configure stop with a message when both RECONVERSE and RANDOMIZED_MSGQ are set, and adds a paragraph to the "Randomized Message Queueing" section of the manual describing the reconverse run-time flags.

./build charm++ reconverse-darwin-arm8 --with-production --enable-randomized-msgq -j8:

CMake Error at CMakeLists.txt:287 (message):
  --enable-randomized-msgq is a classic Converse build option and does
  nothing on reconverse.  Reconverse randomizes at run time instead: run the
  program with +randomized_msgq (and +randomized_seed <N> to repeat the
  draws).


-- Configuring incomplete, errors occurred!

Without the flag, configure completes ("Configuring done", "Build files have been written") and compilation starts as before.

🤖 Generated with Claude Code

The option only affects classic Converse's scheduler queue, which
reconverse builds do not compile, so it was accepted and did nothing.
Reconverse randomizes at run time with +randomized_msgq, so the
configure step now says so and stops. Manual updated.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@lvkale
lvkale merged commit 15ace0a into reviewed-with-reconverse Oct 12, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants