set processor command

[Romain Berrendonner <berrendo@ACT-Europe.FR>]

Hi folks,

I did a small comparison between gdb 5.0, 5.1 and gdb 5.2.1 (configured as
--target=powerpc-unknown-elf, solaris hosted) regarding the 'set processor'
command. The output is:

gdb 5.0:
--------
GDB knows about the following PowerPC and RS6000 variants:
  ppc-uisa  PowerPC UISA - a PPC processor as viewed by user-level code
  rs6000    IBM RS6000 ("POWER") architecture, user-level view
  403       IBM PowerPC 403
  403GC     IBM PowerPC 403GC
  505       Motorola PowerPC 505
  860       Motorola PowerPC 860 or 850
  601       Motorola PowerPC 601
  602       Motorola PowerPC 602
  603       Motorola/IBM PowerPC 603 or 603e
  604       Motorola PowerPC 604 or 604e
  750       Motorola/IBM PowerPC 750 or 740

gdb 5.1:
--------
Requires an argument. Valid arguments are rs6000:6000, rs6000:rs1, rs6000:rsc, rs6000:rs2, powerpc:common, powerpc:603, powerpc:EC603e, powerpc:604, powerpc:403, powerpc:601, powerpc:620, powerpc:630, powerpc:a35, powerpc:rs64ii, powerpc:rs64iii, powerpc:7400, powerpc:MPC8XX, auto.

gdb 5.2.1:
----------
Requires an argument. Valid arguments are rs6000:6000, rs6000:rs1, rs6000:rsc, rs6000:rs2, powerpc:common, auto.

As you may see, the definition of the variants of powerpc vary considerably
from one version to another, and I would like to know what will be the
futur of this command: it looks like it is being deprecated, with less and
less variants supported. Is that true ? Or is it only that the existing code
is more generic ?

Thanks,

-- 
Romain