Searched hist:7674 (Results 1 - 5 of 5) sorted by relevance

/gem5/src/python/m5/objects/
H A D__init__.py7674:8e3734851770 Thu Sep 09 17:15:00 EDT 2010 Nathan Binkert <nate@binkert.org> init: don't build files that centralize python and swig code

Instead of putting all object files into m5/object/__init__.py, interrogate
the importer to find out what should be imported.
Instead of creating a single file that lists all of the embedded python
modules, use static object construction to put those objects onto a list.
Do something similar for embedded swig (C++) code.
/gem5/src/sim/
H A Dinit.hhdiff 7674:8e3734851770 Thu Sep 09 17:15:00 EDT 2010 Nathan Binkert <nate@binkert.org> init: don't build files that centralize python and swig code

Instead of putting all object files into m5/object/__init__.py, interrogate
the importer to find out what should be imported.
Instead of creating a single file that lists all of the embedded python
modules, use static object construction to put those objects onto a list.
Do something similar for embedded swig (C++) code.
H A Dinit.ccdiff 7674:8e3734851770 Thu Sep 09 17:15:00 EDT 2010 Nathan Binkert <nate@binkert.org> init: don't build files that centralize python and swig code

Instead of putting all object files into m5/object/__init__.py, interrogate
the importer to find out what should be imported.
Instead of creating a single file that lists all of the embedded python
modules, use static object construction to put those objects onto a list.
Do something similar for embedded swig (C++) code.
/gem5/src/python/
H A DSConscriptdiff 7674:8e3734851770 Thu Sep 09 17:15:00 EDT 2010 Nathan Binkert <nate@binkert.org> init: don't build files that centralize python and swig code

Instead of putting all object files into m5/object/__init__.py, interrogate
the importer to find out what should be imported.
Instead of creating a single file that lists all of the embedded python
modules, use static object construction to put those objects onto a list.
Do something similar for embedded swig (C++) code.
/gem5/src/
H A DSConscriptdiff 7674:8e3734851770 Thu Sep 09 17:15:00 EDT 2010 Nathan Binkert <nate@binkert.org> init: don't build files that centralize python and swig code

Instead of putting all object files into m5/object/__init__.py, interrogate
the importer to find out what should be imported.
Instead of creating a single file that lists all of the embedded python
modules, use static object construction to put those objects onto a list.
Do something similar for embedded swig (C++) code.

Completed in 102 milliseconds