This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
tdep/1395: Rgdbarch_register_osabi machine wildcard (-1)
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 25 Sep 2003 20:55:23 -0000
- Subject: tdep/1395: Rgdbarch_register_osabi machine wildcard (-1)
- Reply-to: ac131313 at redhat dot com
>Number: 1395
>Category: tdep
>Synopsis: Rgdbarch_register_osabi machine wildcard (-1)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: maintenance
>Submitter-Id: net
>Arrival-Date: Thu Sep 25 20:58:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
The OSABI gdbarch_register_osabi requires an explicit machine. Typically "0" is used, but often it turns out (through hook and crook) to not be compatible. On ppc64, for instance, bfd_arch_ppc/0 gets mapped onto bfd_mach_ppc64.
Suggest adding support for a "wildcard" machine (probably -1) that lets the caller specify that the hook should be called for any processor variant of that class.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: