[gem5-dev] Change in gem5/gem5[develop]: arch-power: Use 64-bit registers and operands

Boris Shingarov has submitted this change. ( https://gem5-review.googlesource.com/c/public/gem5/+/40881 ) Change subject: arch-power: Use 64-bit registers and operands .. arch-power: Use 64-bit registers and operands This inc

[gem5-dev] Re: tutorial docs

If you (or the documentation) expect things to work in a particular way, one thing I've seen in some technical books I've read is that the examples they have in the text are actually runnable, and they have a process which goes through and runs them to make sure they work. Alternatively (and more s

[gem5-dev] Change in gem5/gem5[develop]: arch-power: Refactor CR field generation

Boris Shingarov has submitted this change. ( https://gem5-review.googlesource.com/c/public/gem5/+/42943 ) Change subject: arch-power: Refactor CR field generation .. arch-power: Refactor CR field generation This splits the ex

[gem5-dev] Change in gem5/gem5[develop]: systemc: Extend TlmBridges to 512 bits

Yu-hsin Wang has uploaded this change for review. ( https://gem5-review.googlesource.com/c/public/gem5/+/44528 ) Change subject: systemc: Extend TlmBridges to 512 bits .. systemc: Extend TlmBridges to 512 bits Change-Id: I41

[gem5-dev] Re: tutorial docs

I have verified that the tutorial works in its original form on 20.0.0.3 and in its new form on 20.1.0.5 It segfaults on the current stable master: 21.0.0.0 On Thu, Apr 15, 2021 at 8:18 AM Jason Lowe-Power wrote: > Hi Mike, > > It's a bit embarrassing how out of date our documentation is. > U

[gem5-dev] Change in gem5/gem5[develop]: gpu-compute: Topology and driver changes for dGPU

Alex Dutu has submitted this change. ( https://gem5-review.googlesource.com/c/public/gem5/+/42214 ) Change subject: gpu-compute: Topology and driver changes for dGPU .. gpu-compute: Topology and driver changes for dGPU New to

[gem5-dev] Re: tutorial docs

Hi Mike, It's a bit embarrassing how out of date our documentation is. Unfortunately, we have a really hard time finding the resources or convincing developers to update the documentation as the code changes. The canonical documentation can be found here: http://www.gem5.org/documentation/ and th

[gem5-dev] tutorial docs

Hi, do we (I) have edit permissions on the tutorial documentation? I tried to follow the first steps of the tutorial, and the instructions are out of date for the develop head. Some googling resulted in the solution, but for me it still does not execute correctly. It looks like there are Jira iss

[gem5-dev] Jenkins build is back to normal : Compiler-Checks #59

See ___ gem5-dev mailing list -- gem5-dev@gem5.org To unsubscribe send an email to gem5-dev-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[gem5-dev] Change in gem5/gem5[develop]: fastmodel: Remove CortexA76 unpresented resource

Yu-hsin Wang has uploaded this change for review. ( https://gem5-review.googlesource.com/c/public/gem5/+/44527 ) Change subject: fastmodel: Remove CortexA76 unpresented resource .. fastmodel: Remove CortexA76 unpresented reso

[gem5-dev] Re: gem5 namespace

My vote goes to 1 and A as well My sole argument is consistency; in general I'd rather start a namespace with a lowercase. So that when we have something like a scope resolution we know we are dealing with a namespace and not a class. But that's off-topic. Namespace names are anyway not covered

[gem5-dev] Change in gem5/gem5[develop]: misc: Replace std::conditional with std::conditional_t

Giacomo Travaglini has submitted this change. ( https://gem5-review.googlesource.com/c/public/gem5/+/44506 ) Change subject: misc: Replace std::conditional with std::conditional_t .. misc: Replace std::conditional with std::co

[gem5-dev] Change in gem5/gem5[develop]: misc: Fix VecPredReg coding style

Giacomo Travaglini has submitted this change. ( https://gem5-review.googlesource.com/c/public/gem5/+/44505 ) Change subject: misc: Fix VecPredReg coding style .. misc: Fix VecPredReg coding style * get_bits -> getBits * set_b

[gem5-dev] Re: gem5 namespace

My vote is for 1 and A. We have style rules for a reason, and that is because not following them causes technical problems like name collisions, and makes it less obvious when reading code what things are and what they're doing. It's a bit hypocritical to say that we should follow style rules and

[gem5-dev] Change in gem5/gem5[develop]: dev: Fix GCN3_X86 builds on aarch64 host

Giacomo Travaglini has submitted this change. ( https://gem5-review.googlesource.com/c/public/gem5/+/44485 ) Change subject: dev: Fix GCN3_X86 builds on aarch64 host .. dev: Fix GCN3_X86 builds on aarch64 host Signed-off-by:

[gem5-dev] Change in gem5/gem5[develop]: cpu: Increased the upper bound of cpu issue width

Han-sheng Liu has submitted this change. ( https://gem5-review.googlesource.com/c/public/gem5/+/44225 ) Change subject: cpu: Increased the upper bound of cpu issue width .. cpu: Increased the upper bound of cpu issue width Th