[gem5-dev] Cron /z/m5/regression/do-regression quick

* build/ARM/tests/opt/quick/fs/10.linux-boot/arm/linux/realview-switcheroo-atomic: FAILED! * build/ARM/tests/opt/quick/fs/10.linux-boot/arm/linux/realview-simple-atomic: FAILED! * build/ARM/tests/opt/quick/fs/10.linux-boot/arm/linux/realview-simple-atomic-checkpoint: FAILED!

[gem5-dev] Cron /z/m5/regression/do-regression quick

* build/ARM/tests/opt/quick/fs/10.linux-boot/arm/linux/realview-switcheroo-atomic: FAILED! * build/ARM/tests/opt/quick/fs/10.linux-boot/arm/linux/realview-simple-timing: FAILED! * build/ARM/tests/opt/quick/fs/10.linux-boot/arm/linux/realview-simple-atomic-checkpoint: FAILED!

[gem5-dev] Change in gem5/gem5[master]: tests: Updated tests to download from http://dist.gem5.org

Bobby R. Bruce has submitted this change. ( https://gem5-review.googlesource.com/c/public/gem5/+/24548 ) Change subject: tests: Updated tests to download from http://dist.gem5.org .. tests: Updated tests to download from

Re: [gem5-dev] Memory fence neglected/obviated after squashing a younger/later fence

Hey Eduardo, From a quick skim, I think what you are describing makes sense, and your solution sounds like it's on the right track. Instead of attaching to email (which is stripped on this mailing list), could you please create a changeset on gerrit. See http://new.gem5.org/contributing and

Re: [gem5-dev] RFC: Removing authors from file headers

This would be OK with me. However, I think it should be coupled with us writing good release notes with each release which gives the code contributors credit for their contributions. IIRC, the purpose of the "author" field was to know who to call when things broke. I agree that this purpose has