Ack. After thinking about it a bit, I think a minor rename of the riscv
version is the right approach for right now.
Gabe
___
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
+1 for renaming the VirtIOMMIO to be ISA-specific.
Making packages in python is a good long-term goal, but right now, I think
it would cause more problems than it would solve.
Cheers,
Jason
On Tue, Sep 14, 2021 at 4:54 AM Gabe Black wrote:
> Just FYI, I'm working on pushing env['TARGET_ISA']
Just FYI, I'm working on pushing env['TARGET_ISA'] == 'foo' checks out of
SCons, and I almost have it working except that both arm and riscv define
VirtIOMMIO.py SimObject files which conflict with each other since they
take the same slot in m5.objects. You could reasonably blame that on
Hey Gabe,
I completely agree with you that hierarchy in the Python code would be
better! This is in part why we're working on the components library. The
problem is supporting backwards compatibility.
Cheers,
Jason
On Fri, Aug 13, 2021 at 5:49 PM Gabe Black wrote:
> Ok, it sounds like listing
Ok, it sounds like listing out the contents of the SimObject files is not
going to be a problem then, and I'll plan on doing that.
*I* still like the idea of adding hierarchy (this is why python has
packages, c++ has namespaces, almost all modern languages have similar
features, etc), but
Hey Gabe,
Some responses inline below.
On Thu, Aug 12, 2021 at 9:37 PM Gabe Black via gem5-dev
wrote:
> Hey folks, here are some of my thoughts on the SimObject() mechanism in
> SCons, and the structure of the m5.objects package.
>
> Right now, when you put a SimObject('foo.py') line in a
