This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gdb/430: Invert the sim-state -> sim-cpu relationship



>Number:         430
>Category:       gdb
>Synopsis:       Invert the sim-state -> sim-cpu relationship
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Mar 16 08:38:20 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
The existing sim/common framework very much puts sim-state in the middle and above sim-cpu.  I think the rationale was that this would allow better performance in the single cpu case (that was ~4 years ago :-) this made it possible to access everything using a single (SD) pointer.

In the SMP case, things are half inverted - both SD and CPU are passed around.

Suggest inverting this relationship so that sim-cpu is always at the core.  If a given sim-cpu needs sim-state information then it can be included in the sim-cpu.

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]