[gem5-dev] gem5 Workshop @ISCA 2025: Announcement and call-for-presentations

Dear all, I'm happy to announce the upcoming gem5 Workshop, scheduled to take place on June 22, 2025, in conjunction with ISCA 2025 in Tokyo, Japan. This full-day event offers a platform for researchers, developers, and users to share insights, present their work, and engage in discussions that

[gem5-dev] v24.1 staging branch scheduled for Nov 6th; release on Nov 22nd

Dear all, In order to release v24.1 of gem5 on November 22nd, we are planning to create the v24.1 `staging` branch on November 6th (next Wednesday). As a reminder of our release procedures, the `staging` branch is created from the gem5 `develop` branch two weeks before a gem5 release. This two

[gem5-dev] gem5 Tutorial at HPCA '24

Hey all, On March 2nd we will be holding the 6th gem5 Tutorial at HPCA '24 in Edinburgh, Scotland. This will be a full-day event and will focus on teaching those new to gem5 how to use the latest version. It will be a day-long “crash course” in gem5 and assume no prior knowledge of using compu

[gem5-dev] Re: gem5 Developers' Meeting: December 14th, 5pm (UTC)

This is a friendly reminder that the gem5 Developers meeting is scheduled for December 14th at 5pm (UTC). Anyone is free to attend. Zoom meetings and updates about this event can be found on the gem5 Discussions page: https://github.com/orgs/gem5/discussions/661 -- Dr. Bobby R. Bruce Room 3050

[gem5-dev] gem5 Developers' Meeting: December 14th, 5pm (UTC)

Dear all, https://github.com/orgs/gem5/discussions/661 The gem5 Developers' Meeting is scheduled for December 14th at 5pm (UTC). Zoom link details and meeting agenda information can be found in the above link to the GitHub Discussions page. Anyone who wishes to attend may attend. Kind regards,

[gem5-dev] Creation of gem5 v23.1.0.0 staging branch scheduled for December 1st

Hey all, As discussed and agreed upon during our November Developer meeting (https://github.com/orgs/gem5/discussions/482), we have scheduled the creation of our staging branch from `develop` for December 1st. This means **gem5 developers have until December 1st to have their contributions merg

[gem5-dev] GitHub Discussion about dropping Gerrit Change-ID requirement

https://github.com/orgs/gem5/discussions/324 (Note: I won't act on this without good buy-in from the community. I'd like to know what works best for everyone). -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net

[gem5-dev] Re: Make m5 internals available to Python interpreter (for syntax highlighting in vscode)

I've created a pull request here which should help: https://github.com/gem5/gem5/pull/307. From playing around with this mypy.stubgen fix, it helps the Pylance IntelliSence but it isn't complete. What's notably lacking are doc-strings (so methods, classes, etc don't have documentation on argume

[gem5-dev] Join th discussion on gem5's PR Merge policy

I've started a discussion on GitHub Discussions regarding the gem5 PR Merge Policy and possible improvements: https://github.com/orgs/gem5/discussions/261 Please feel free to join and give input or feedback. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://ww

[gem5-dev] Re: Hotfix v23.0.0.1: To fix GCN3_X86 compilation

Thanks for this. The Hotfix was made this afternoon and is now on the stable branch. Note: We have no officially moved to the GitHub repo: https://github.com/gem5/gem5. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net > On Jul 10, 2023,

[gem5-dev] Hotfix v23.0.0.1: To fix GCN3_X86 compilation

Dear all, I’m planning a hot fix to the v23.0.0 release to address an error found. The issue was highlighted here https://gem5.atlassian.net/browse/GEM5-1332. In short, the v23.0.0.0 release can’t compile the “build/GCN3_X86/gem5.opt” binary. This came about as we cherry-picked some GPU patches

[gem5-dev] Re: Build failed in Jenkins: nightly #659

This appears to be a Docker failure of some kind. Both the compiler and nightly tests dropped at the same time. I think the Docker daemon crashed for some reason No tests failed here. The patches submitted yesterday don’t interact with any tests so they should all still pass. I’ll re-run these

[gem5-dev] Re: [Important Announcement] gem5 Migration from Gerrit to GitHub

Dear all, We’re still working on ensuring a smooth migration from Gerrit to Github. We had originally planned to have migration occur yesterday, on the 15th, but found we still need to update documentation and do some further checks to ensure the GitHub testing infrastructure meet our requireme

[gem5-dev] Re: v23.0 staging branch to be created on May 24th

Dear all, As you have probably noticed, we’re already over our original June 9th scheduled release of v23.0. The staging branch periods has been productive and allowed us to test and fix many parts of the project. We still require a little more time with this so are now aiming to have the relea

[gem5-dev] [gem5 on GitHub] Explaining our new testing infrastructure: GitHub Actions, Runners, and current limitations

Dear all, As you are likely aware, we will be migrating to GitHub, form Gerrit, soon. Some have reached out to me with questions about the testing infrastructure on GitHub and how it may be used and improved. I shall do so in this email. GitHub allows for testing via its “Actions” infrastructur

[gem5-dev] [Important Announcement] gem5 Migration from Gerrit to GitHub

Dear all, We are excited to inform you that gem5 is migrating from Gerrit to GitHub for code collaboration and version control. This migration is scheduled to take place on June 15th. We believe that this move will provide a more streamlined and efficient development process for our community.

[gem5-dev] Re: Build failed in Jenkins: nightly #620

> I’m confused, there weren’t any recent GPU commits, right? So someone other > than Matt P or us must have broken things? > > Matt > > On Wed, May 31, 2023 at 3:19 PM Bobby Bruce via gem5-dev <mailto:gem5-dev@gem5.org>> wrote: > Hey Matt, >

[gem5-dev] Re: Build failed in Jenkins: nightly #620

Hey Matt, At least one of the reason’s the Nightly tests are failing is a GPU test failure. You can reproduce it using: ``` wget -qN http://dist.gem5.org/dist/develop/test-progs/square/square docker run --rm -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) gcr.io/gem5-test/gcn-gpu:latest

[gem5-dev] Re: v23.0 staging branch to be created on May 24th

Dear all, As of this afternoon, the gem5 v23.0 staging branch has been created. This branch will be intensely tested over the next couple of weeks to ensure it's ready to be merged into the stable branch. The release of gem5 v23.0 (the point at which the staging branch is merged into the stable

[gem5-dev] Re: Build failed in Jenkins: nightly #612

I’ve fixed the nightly failures with this patch: https://gem5-review.googlesource.com/c/public/gem5/+/70860 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net > On May 21, 2023, at 5:04 PM, jenkins-no-reply--- via gem5-dev > wrote: > > Se

[gem5-dev] v23.0 staging branch to be created on May 24th

Dear all, I am writing to inform the community that we are planning to create the staging branch for v23.0 on May 24th. This branch will be created from the develop branch and intensively tested prior to merging into the stable branch, thereby completing the release of v23.0. The staging branch

[gem5-dev] Re: gem5 Workshop @ISCA '23: Call for Presentations

Dear all, This is a friendly reminder that the submission deadline for gem5 Workshop presentation proposals is one week away: Monday, April 24th (AOE). If you are interested in presenting at the workshop then please email me ( bbr...@ucdavis.edu) with the following: * Title of the presentation. *

[gem5-dev] Re: Build failed in Jenkins: nightly #571

The following patch should fix this nightly bug: https://gem5-review.googlesource.com/c/public/gem5/+/69717 There was a small bug introduced where header files were not being added to the “build” directory. This broke the SST compilation as it uses the “build” directory as a include path. In a

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #570

The two patches in this relation-chain should fix the compilation error: https://gem5-review.googlesource.com/c/public/gem5/+/69598 In short: the CPP Filesystem library needs a couple of work-arounds to compile successfully with GCC Versions 7 and 8. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall

[gem5-dev] Re: Build failed in Jenkins: nightly #566

I don’t know the exact cause of this problem but it’s a Docker failure of some kind and likely not due to any actual test failure. These just happen very so often on our Jenkin’s setup and they are impossible to recreate locally. It could be Docker running out of member (though it should have am

[gem5-dev] Re: Building on Apple Silicon / ARM docker

Also, I don’t fully understand the docker issues you are facing. Could you send us the actual docker commands you are running so I can try to reproduce the error? The images we provide should work (perhaps there is some incompatibility with running them on Mac, but if this is the case I’ve yet t

[gem5-dev] Re: Building on Apple Silicon / ARM docker

Hey, I believe I’ve run into this issue before on my Apple machine and have a solution. I am running on the assumption here your Python installation is 3.11. That’s the only reason I can see as to why you’d have this problem (this email may be pretty pointless if this assumption isn’t true). In

[gem5-dev] Our use of Python Ply is incompatible with Python 11

Hey all, In November 2022 Python 3.11 was release and is slowly being rolled out for usage. In January of this year I became aware of an issue which makes gem5 incompatible with Python 3.11. I’ve outlined my findings, in detail, here: https://gem5.atlassian.net/browse/GEM5-1321. In brief, Pyth

[gem5-dev] Re: Build failed in Jenkins: nightly #509

Gabriel, It looks like the nightly tests failed due to some of the ports not being updated correctly. Do you have time to look into this and fix it? Kind regards, Bobby -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Fri, Feb 3, 2023 a

[gem5-dev] Re: Build failed in Jenkins: nightly #482

Sorry for the delay. Yesterday I cleared up some space on the server. We shouldn't see space issue again. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Thu, Jan 12, 2023 at 7:04 PM Matt Sinclair wrote: > Hi Bobby, > > Just checking

[gem5-dev] Re: Build failed in Jenkins: weekly #99

Thanks Matt! I've restarted the Weeklys to ensure it's now working. Should be complete over the next day or two. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Sun, Jan 8, 2023 at 12:48 AM Matt Sinclair via gem5-dev < gem5-dev@gem5.or

[gem5-dev] gem5 v22.1 released!

Dear all, v22.1 gem5 has officially been released! You can use `git clone https://gem5.googlesource.com/public/gem5` to obtain the latest release and consult the RELEASE-NOTES.md for a high-level overview of significant changes. I'll be working on a b

[gem5-dev] v22.1 staging branch ready. RELEASE_NOTES.md requiring feedback

Dear all, After rigorous testing, we've decided the v22.1 staging branch is of a good enough state to be merged into the stable branch (The staging branch can be obtained with `git clone -b release-staging-v22-1 https://gem5.googlesource.com/public/gem5`). The only outstanding task is to update t

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #457

This one is my fault. This should fix the problem: https://gem5-review.googlesource.com/c/public/gem5/+/66772 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Sat, Dec 17, 2022 at 4:53 AM jenkins-no-reply--- via gem5-dev < gem5-dev@gem5.

[gem5-dev] Re: Build failed in Jenkins: nightly #446

I believe this patch should fix the nightly build: https://gem5-review.googlesource.com/c/public/gem5/+/66512 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Sun, Dec 4, 2022 at 11:02 PM jenkins-no-reply--- via gem5-dev < gem5-dev@gem5.

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #435

I don't know exactly what patch triggered this bug, but gcc-12 was failing to compile gem5 due to a missing virtual destructor in GlobalSyncEvent. This patch should fix the problem: https://gem5-review.googlesource.com/c/public/gem5/+/66152 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis D

[gem5-dev] Re: Build failed in Jenkins: nightly #429

Fixed with: https://gem5-review.googlesource.com/c/public/gem5/+/65871 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Mon, Nov 21, 2022 at 12:31 PM jenkins-no-reply--- via gem5-dev < gem5-dev@gem5.org> wrote: > See

[gem5-dev] Re: Build failed in Jenkins: nightly #413

gt;> > >> > >> > >> I have seen this issue with do_boot_cpu as well. The short story is I > had to use multiple event queues and set the “sim_quantum” of the Root > object to 1e8: https://gem5-review.googlesource.com/c/public/gem5/+/65131. > Note that 1e8 is different from the 1

[gem5-dev] Re: Build failed in Jenkins: nightly #413

o use multiple event queues and set the “sim_quantum” of the Root object to 1e8: https://gem5-review.googlesource.com/c/public/gem5/+/65131. Note that 1e8 is different from the 1e9 value used elsewhere in gem5. Based on a test of doing 100 boots with 4 CPUs, 1e8 booted all four CPUs every time and

[gem5-dev] Re: Build failed in Jenkins: nightly #413

Hey all, I've submitted the following patch to Gerrit which should fix the timeout issues we're seeing with the Jenkin's nightly build: https://gem5-review.googlesource.com/c/public/gem5/+/65492. The high level summary of the problem is as follows: - Up until recently we were using "m5 Simulator

[gem5-dev] Re: Build failed in Jenkins: nightly #413

It turns out this patch: https://gem5-review.googlesource.com/c/public/gem5/+/64831 is greatly increasing the Linux boot times and therefore causing the timeouts to occur. I'll try to find a solution for this. Unfortunately reverting the patch isn't an option, changing the CPUID is necessary to run

[gem5-dev] v22.1 Staging branch created

Dear all, As of this afternoon, the gem5 v22.1 staging branch has been created. This branch will be intensely tested over the next couple of weeks to ensure it's ready to be merged into the stable branch. If you have any bug fixes you can submit them to the develop branch then cherry-pick the cha

[gem5-dev] Re: Build failed in Jenkins: nightly #403

At least one problem here is the Nightly tests are failing due to it reaching timeout. I've submitted some patches here to remove some of the Boot tests (we have a lot of these, they take a while to run, and are largely doing the same thing), remove a couple of tests that require compilation of SP

[gem5-dev] Re: Build failed in Jenkins: weekly #46

This test actually failed with an error message: ``` FileExistsError: [Errno 17] File exists: '/nobackup/jenkins/workspace/weekly/tests/gem5/resources' At: /usr/lib/python3.8/os.py(228): makedirs build/GCN3_X86/python/gem5/resources/resource.py(156): __init__ /nobackup/jenkins/workspace/week

[gem5-dev] Re: Upcoming gem5 events! Tutorial, Workshop, and Boot Camp!

Dear all, This is a friendly reminder that the deadline for submitting a presentation proposal to the gem5 users' workshop is April 26th. The presentation proposal submission link is here: https://forms.gle/VZxXsWBniUPGBQdw5 The gem5 users' workshop will be co-located with ISCA '22 (New York City

[gem5-dev] Re: gem5 v22.0 to be released in early May. Staging branch to be created by the end of April

Dear all, We intend to create the staging branch on April 28th, with the intent of releasing gem5 v22.0 in early May. This is a two week warning. Please ensure all your patches you wish to be part of v22.0 are submitted to the develop branch prior to April 28th. Kind regards, Bobby -- Dr. Bobby R

[gem5-dev] Re: Build failed in Jenkins: nightly #193

Hoa, Looks like you broke the tests with this commit: https://gem5-review.googlesource.com/c/public/gem5/+/58790. You should've removed the `root = Root(full_system=True, system=board)` line, this is set when you execute simulator.run() Can you push a quick fix (and run it to make sure it works)?

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #189

I think we need to have a little discussion on this. The problem with increasing the scons version is we support Ubuntu 18.04 (Official end-of-support not until April 2023) which if you run `apt install scons` will give you v3.0.1. So, increasing this the scons version requirements will hurt these

[gem5-dev] Re: Build failed in Jenkins: nightly #183

My fault. Fixed here: https://gem5-review.googlesource.com/c/public/gem5/+/58609 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, Apr 5, 2022 at 2:05 AM jenkins-no-reply--- via gem5-dev < gem5-dev@gem5.org> wrote: > See < > https:/

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #189

I don't fully understand the issue, but after doing a bisect, the commit causing these issues is https://gem5-review.googlesource.com/c/public/gem5/+/58356. To reproduce locally: ``` docker run -u $UID:$GID --rm -v $(pwd):$(pwd) -w $(pwd) gcr.io/gem5-test/clang-version-9 python3 /usr/bin/scons bu

[gem5-dev] gem5 v22.0 to be released in early May. Staging branch to be created by the end of April

Dear all, In line with our policy of having three major releases a year, we're aiming to have v22.0 of gem5 released in early May. This means we'll be creating a staging branch from the develop branch by the end of April. The staging branch will be intensely tested to ensure it is suitable for ge

[gem5-dev] Upcoming gem5 events! Tutorial, Workshop, and Boot Camp!

Dear all, We wish to make the computer architecture research community aware of several gem5 events occurring over the next 6 months. There will be two events co-located at ISCA 2022 (held in New York, June 18th) -- a 3 hour tutorial, and a 3 hour workshop. In July, there will be a "gem5 Boot Camp

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #187

Gabe, It seems like this patch: https://gem5-review.googlesource.com/c/public/gem5/+/56892 is causing the compilation failure. I've left a comment there. The TL;DR: when compiling with our minimum dependencies (no optional packages), we get `Error: Got protobuf to build, but lacks support!`. I ass

[gem5-dev] Re: Build failed in Jenkins: nightly #172

I'm frustrated that I don't know why this error is occurring and Google is of little help. This appears to be nothing to do with the actual tests but some fault with Docker. My only guess is the Docker container, in this case, is running out of memory, so I've increased it via this patch: https://

[gem5-dev] Re: Build failed in Jenkins: nightly #166

It seems like the tests were failing due to the Plots plugin running into an error: https://jenkins.gem5.org/job/nightly/166/console. I have disabled this and suspect the Nightly tests should pass now. @Giacomo: Any idea what's going on here? Though I've turned this off, i've taken note of the val

[gem5-dev] Re: Build failed in Jenkins: weekly #33

These two tests failed on jenkins with very similar errors: ``` JSONDecodeError: Unterminated string starting at: line 266 column 31 (char 12245) At: /usr/lib/python3.8/json/decoder.py(355): raw_decode /usr/lib/python3.8/json/decoder.py(337): decode /usr/lib/python3.8/json/__init__.py(357):

[gem5-dev] Re: Build failed in Jenkins: nightly #157

Our compiler tests also failed with a docker error: https://jenkins.gem5.org/job/compiler-checks/166/console I'm guessing the Nightly tests momentarily killed the Docker service and caused the compiler tests to fail? -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: ht

[gem5-dev] Re: Build failed in Jenkins: nightly #156

I have no idea why this failed. This is building the GPU GCN3_x86 (in the docker container), and it says it failed at the linking stage. I can't recreate this locally. I'm going to run it again. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.ne

[gem5-dev] Re: All tests failing: Please don't commit anything!

Pretty sure the compiler tests are fixed, but they are re-running, so let's see. The nighty tests succeeded in the last couple of runs. Either what was pushed before this submission freeze fixed the issue (I don't know exactly how), or the test is flaky in some capacity. I'm letting it run again t

[gem5-dev] Re: resource downloader failure

I've added some code that should help here: https://gem5-review.googlesource.com/c/public/gem5/+/57275 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, Mar 1, 2022 at 10:41 AM Bobby Bruce wrote: > I'll change my answer slightly: I

[gem5-dev] Re: resource downloader failure

I'll change my answer slightly: It seems like this error is happening from trying to download the resources.json file (hosted in the resources repo) too much. I suspect there are similar restrictions here. I think I can fix it too. I'll probably add a wait-and-retry for the resource downloader any

[gem5-dev] Re: resource downloader failure

Nice find Gabe. That would certainly explain a lot. Turns out there's a 50Gbps quota that will return a 429 error if hit: https://cloud.google.com/storage/quotas. I'll see if I can get this increased and, either way, I'll implement a wait-and-retry strategy in the downloader for when this error is

[gem5-dev] Re: Build failed in Jenkins: nightly #135

Hey Matt, Did you get a chance to look into this? -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, Feb 22, 2022 at 8:20 AM Poremba, Matthew via gem5-dev < gem5-dev@gem5.org> wrote: > [AMD Official Use Only] > > Yes, I will take a

[gem5-dev] gem5 v21.2.1 released!

Dear all, A minor release, consisting of bug fixes and small improvements to v21.2 of gem5, is now available. Users can obtain this release by pulling the latest changes from the "stable" branch of the gem5 repository: https://gem5.googlesource.com/public/gem5. A short list outlining the changes

[gem5-dev] Re: microcode test system

Hey Gabe, To answer your testing query, we do have some stuff setup to run python test. We use Python's 'unittest' module for this ( https://docs.python.org/3.8/library/unittest.html). In our setup "tests/run_pyunit.py" is run as part of our quick/kokoro tests with NULL/gem5.opt (i.e., behind the

[gem5-dev] Re: gem5 Minor release v21.2.1: Candidate patches

Dear all, Haven't heard much, or anything, from this. I'm going to take this as a quiet thumbs up from the community. I'm planning to release v21.1.2 on Tuesday, so there are still a few more days to protest, ask questions, propose other patches, etc. Kind regards, Bobby -- Dr. Bobby R. Bruce Ro

[gem5-dev] Re: Kokoro failures

Hey Giacomo, For the first two patches I can't access the failing Kokoro due to re-runs overwriting the log. In the last one, https://gem5-review.googlesource.com/c/public/gem5/+/56303/1, I'm not seeing a timeout issue. That appears to be my aforementioned issue, which I've come to guess is due to

[gem5-dev] Re: Kokoro failures

Are there examples of this timeout happening recently? I can't see any over the past week. There's a separate issue affecting one of Gabe's patches that I'm looking into (here: https://gem5-review.googlesource.com/c/public/gem5/+/56303) but these appear to be due to dynamic libraries not linking c

[gem5-dev] gem5 Minor release v21.2.1: Candidate patches

Dear all, In the last month, since v21.2 has been released, gem5 contributors have fixed bugs and added improvements which I believe should be included as part of the v21.2 release. I've therefore decided to bundle these patches as part of a gem5 minor release; v21.2.1. I've been keeping track of

[gem5-dev] gem5 v21.2 released!

Dear all, gem5 v21.2.0.0 has officially been released. You can use `git clone https://gem5.googlesource.com/public/gem5` to obtain the latest release and consult the RELEASE-NOTES.md for a high-level overview of significant changes: https://gem5.google

[gem5-dev] v21.2 staging branch created; v21.2 release scheduled for Dec 21st

Dear all, The v21.2 staging branch has been created. Thank you to everyone who worked hard over the past week to get their changes into the develop branch. We'll still be accepting bug-fix changes to the v21.2 staging branch. Kind regards, Bobby -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC D

[gem5-dev] Re: Broken SST due to python changes

Hey gabe. No idea if this is the _best_ solution to your problem, but my solution would be to rebuild the image with this installed. Modify the `util/dockerfiles/sst-11.1.0/Dockerfile` to the environment you want. Then run `docker build -t util/dockerfiles/sst-11.1.0` to build an image with the n

[gem5-dev] Re: Broken SST due to python changes

Thanks Gabe, This is very much appreciated. I'm going to create the release staging once a couple more things get in. Feel free to push any patches related to these bugs to the release staging branch. If there is an order of priority I'd say the bug affecting SST is of higher importance than that

[gem5-dev] Re: Broken SST due to python changes

Hey Gabe, Is there any update on this? Kind regards, Bobby -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Dec 8, 2021 at 5:51 PM Hoa Nguyen via gem5-dev wrote: > Hi Gabe, > > I have more details about this. In this use case, SS

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #71

Fix here: https://gem5-review.googlesource.com/c/public/gem5/+/53823 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Dec 8, 2021 at 12:42 AM jenkins-no-reply--- via gem5-dev < gem5-dev@gem5.org> wrote: > See < > https://jenkins.gem

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #65

Fix here: https://gem5-review.googlesource.com/c/public/gem5/+/53684 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, Dec 7, 2021 at 12:31 AM jenkins-no-reply--- via gem5-dev < gem5-dev@gem5.org> wrote: > See < > https://jenkins.ge

[gem5-dev] v21.2 staging branch to be created on Wednesday

Dear all, We are planning on creating a staging branch for v21.2 on Wednesday. I'm aware we've had a lot of changes submitted to Gerrit over the past few months so I am writing to make sure I haven't missed anything important. Please reach out to me directly if you feel a change has been sitting a

[gem5-dev] Re: redundant builds in the long regressions

Hey Gabe, That change is still in review: https://gem5-review.googlesource.com/c/public/gem5/+/53503 I just wanted to get a few more eyes on it before submitting. You are correct, after this is merged we'll no longer need to compile X86_MESI_Two_Level and vanilla X86. Kind regards, Bobby -- Dr.

[gem5-dev] LupIO: Friendly IO Devices for gem5 (reviews appreciated!)

Dear all, Here at UC Davis two undergraduate students, Melissa Jost and Laura Hinman, have been working on incorporating LupIO devices into gem5. For those unaware, LupIO devices were developed by Prof. Joel Porquet-Lupine as a set of open-source I/O devices to be used for teaching. They were des

[gem5-dev] Re: Build failed in Jenkins: nightly #48

That doesn't look like a failure to me, but maybe? The log isn't very helpful here. Either way, here's the potential fix: https://gem5-review.googlesource.com/c/public/gem5/+/52983. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Fri, N

[gem5-dev] Re: failing kvm tests

Took me longer than expected to figure this out, but I eventually got it. A fix is here: https://gem5-review.googlesource.com/c/public/gem5/+/52663. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, Nov 9, 2021 at 4:14 AM Gabe Black

[gem5-dev] Re: failing kvm tests

Yip, I accidentally added some X86 tests to the quick/Kokoro tests. Thanks for pointing that out. The fix can be found here: https://gem5-review.googlesource.com/c/public/gem5/+/52563 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Mon,

[gem5-dev] Re: multi-ISA gem5 proof of concept

Looks good to me. Perhaps this is explained elsewhere, but what's the logic in coupling the CPU Type (Timing, Atomic, o3) with the ISA? Why do we interact with this like `--cpu-type=X86AtomicSimpleCPU` and not `--cpu-type AtomicSimpleCPU --isa=X86`? Current CPU types are switchable during a simula

[gem5-dev] Re: preview branch for mutli-ISA gem5?

I think it's a great idea and we should probably do it more often for this big long changes we don't want to straddle a release. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Thu, Nov 4, 2021 at 7:42 AM Jason Lowe-Power via gem5-dev <

[gem5-dev] Re: failing kvm tests

Hey Gabe, At present our Jenkins doesn't have KVM enabled so I believe no tests that use KVM were being run regularly. I intend to get KVM enabled on the Jenkins server over the next few days. I also found the bugs you were referring to when running the long (nightly) and very-long (weekly) tests

[gem5-dev] Re: gem5 gui tool?

Hey Gabe, The gem5 GUI code is still around, it's on a separate branch in the repo, `feature-gui`: `git clone -b feature-gui https://gem5.googlesource.com/public/gem5`. We at UC Davis tried to get some students to continue working on this, but we were never able to. Hopefully we can get someone t

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #9

Hey Gabe, It seems like both the Nightly and Compiler tests are failing because SPARC no longer compilers. This appears to be due to this change: https://gem5-review.googlesource.com/c/public/gem5/+/48717. It looks like you changed "checkFpEnableFault" to "checkFpEnabled" and didn't update this ev

[gem5-dev] Re: Build failed in Jenkins: nightly #10

In fairness, I think the tests should ideally pass regardless as to where they are executed from, but that's not a priority right now :). -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Oct 13, 2021 at 11:19 AM Matt Sinclair wrote

[gem5-dev] Re: Build failed in Jenkins: nightly #10

Fix for the nightly tests here: https://gem5-review.googlesource.com/c/public/gem5/+/51607 I've verified this fixes the issue. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Oct 13, 2021 at 10:50 AM Bobby Bruce wrote: > Ah, yea

[gem5-dev] Re: Build failed in Jenkins: nightly #10

Ah, yeah, that's probably the problem. For clarity, all the nightly tests do is run `./tests/nightly.sh 16` from the gem5 root. Likewise, all the weekly tests do is run `./tests/weekly.sh 16` from the gem5 root. If you can update the tests with this assumption in mind, they should pass. -- Dr. Bob

[gem5-dev] Jenkins' server moved; https://jenkins.gem5.org now live

Dear all, Our gem5 Jenkins' server has finally found a permanent home at the University of Wisconsin. Prior to this we were hosting here at UC Davis, but this came with restrictions on what we could expose to the wider world (i.e., no website). As such, the https://jenkins.gem5.org/ web portal is

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #211

I can't recreate this error locally. It seems like it's just a hiccup with our Jenkins server. I suspect it'll run correctly tonight. -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Oct 6, 2021 at 12:00 AM jenkins-no-reply--- via g

[gem5-dev] Re: replacement for x86-boot-tests/run_exit.py?

Hey Gabe: Try `tests/gem5/configs/x86_boot_exit_run.py`: https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/tests/gem5/configs/x86_boot_exit_run.py. It should function similarly to the old `run_exit.py` but you don't need to specify the disk and the kernel. Kind regards, Bobby -- Dr

[gem5-dev] Re: failing ARM dual CPU tests?

Hey Gabe, This is very strange and I can't say I've seen this issue before. The problem shouldn't be docker, none of these tests spin up an instance. I was going to suggest deleting the resources (`tests/gem5/resources`) and trying again, but it seems like you've tried that. My only sensible guess

[gem5-dev] Re: name collision between tests/gem5 and built in gem5 module

Personally I've never really liked the directory structure under `tests`. Scripts are often far from the tests that run them. There's also `tests/configs` and `tests/gem5/configs` which could almost certainly be merged. Almost all tests are stored under `tests/gem5` for no other reason than this is

[gem5-dev] Re: Build failed in Jenkins: compiler-checks #197

My bad, fix here: https://gem5-review.googlesource.com/c/public/gem5/+/50829 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Sep 22, 2021 at 3:21 PM jenkins-no-reply--- via gem5-dev < gem5-dev@gem5.org> wrote: > See < > https://jen

[gem5-dev] gem5 v21.1.0.2 hotfix release: Fix Vector statistics

Dear all, The stable branch of the gem5 repository now contains the v21.1.0.2 hotfix release. This release fixes a bug which was causing some vector statistics in gem5 to break. We encourage gem5 users to pull the latest version of gem5 from the repo's stable branch. Kind regards, Bobby -- Dr. Bo

[gem5-dev] Re: Build failed in Jenkins: nightly #440

Fix here: https://gem5-review.googlesource.com/c/public/gem5/+/50128 -- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Sep 8, 2021 at 4:52 AM jenkins-no-reply--- via gem5-dev < gem5-dev@gem5.org> wrote: > See < > https://jenkins.gem

[gem5-dev] gem5 v21.1.0.1 hotfix release: Fix for 'deprecated attribute' warning

Dear all, The stable branch of the gem5 repository now contains the v21.1.0.1 hotfix release. This release fixes a bug where the build output was being flooded with "'deprecated' attribute directive ignored" warnings, as reported here: https://gem5.atlassian.net/browse/GEM5-1063. While this bug ne

[gem5-dev] v21.1.0.1 hotfix: Fix for 'deprecated attribute' warning

Dear all, As some you building on the stable branch may have noticed, there's an annoying bug where the build output is flooded with " 'deprecated' attribute directive ignored" warnings (Jira ticket here: https://gem5.atlassian.net/browse/GEM5-1063). While this doesn't break the build, it is annoy

  1   2   3   >