The staging branch has been created; release pushed to December 5th; Select PRs allowed to be submitted to staging

[BobbyRBruce]

Hey all,

The release staging branch has been created. However, unlike run-ups to previous gem5 releases, this one has had gem5 community members pushing relatively big features, some of which require more time for reviewing, testing, and development back-and-forth. While the original goal was to release v24.1 on November 22nd, doing so would require that the staging branch be ready for intensive testing now.

Given that these features need more time, we’ve decided to push the release to December 5th. While the staging branch has still been created, we will permit these PRs (listen below) to be merged within the next two weeks (as well as any bug fixes). In all cases, the contributors of these have been vocal about their desire to be part of the release and have worked with us to make this happen. Therefore, we’re willing to make an exception to our usual release procedures.

All other contributions to the develop branch (outside of bug fixes) will be assumed for 25.0 and can continue on as normally during this time.

We apologize for not giving ample notice of this release and have noted this as something to improve upon. We would, however, like to thank the great community development effort put into this release nonetheless.

• ruby: Enable all protocols in a single gem5 build #117
• mem-ruby, configs: Add a CHI-TLM controller + testing #1084
• cpu: add GlobalInstTracker and LocalInstTracker #1433
• stdlib: Add viper board, viper cache, and gpu components #1636
• cpu: LoopPoint analysis object #1419
• stdlib: Add interface to set binary in fs mode #1743
• misc: Do not share the random number generator across components #1534
• mem-ruby, sim-se: Add support for Maybe_Stale blocks in functional reads #1489
• python,stdlib: Improve exit event return #947
• arch-riscv: Use getValidAddr to get zero-extend address in RV32 mode #1768
• Illegal instruction with 6.11.3 Kernel #1674
• fix wrong ruby-CHI base class name #1817 : Waiting for tests to pass then will merge.
• stdlib: fix LoopPoint module not getting relative counts #1766 : Waiting for tests to pass then will merge.
• arch-arm: Fix bug in VQRSHL. #1804
• tests: modify gem5/learning-gem5 ref file to fix failure #1795
• mem-ruby: Fix conflict between 117 and 1084 #1813
• arch-x86, sim-se: move mmap end downward in case of large stacks #1810
• misc: update fs examples to use ubuntu 24.04 boot workloads #1491
• mem-ruby, scons: Add ProtocolInfo.hh files in build targets #1829

[Harshil2107]

We should also fix this issue: #1674

[studyztp]

Can this bug fix also be in the staging branch? #1766

[BobbyRBruce]

#1804 should be in too

[giactra]

Hi Bobby, on which branch should I contribute RELEASE_NOTES.md updates?

[BobbyRBruce]

Honestly, either is fine for now. Though you can create PRs targeting the staging branch which may be slightly easier for me.

[erin-le]

PR #1795 fixes the gem5/learning-gem5 daily test failure and should get in

[Harshil2107]

#1480 we should get this in as well to get the new gem5-bridge driver in

[giactra]

I don't want to call a single PR out but that PR has received limited reviews being still in draft state. IMHO we shouldn't rush new WIP features into the staging branch

[powerjg]

You're right, Giacomo. Apologies for not getting this ready for review sooner. We can drop it from the release.

[erin-le]

#1797 and #1810 are bug fixes that were submitted recently and haven't been reviewed.

Giacomo's PR to fix the conflict between multi-Ruby and CHI-TLM: #1813

Also, we previously discussed getting these config script updates in, but they aren't included above: #1491

[Harshil2107]

PR #1829 fixes the build failure when using --duplicate-sources after the new multiruby change. This also fixes the daily test build failure for sst and systemc tests

[erin-le]

#1817 and #1828 are approved bug fixes; putting them here for reference.

[BobbyRBruce]

Staging branch closed. V24.1 released: #1846