From: Elena Zannoni <ezannoni@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Romain Berrendonner <berrendo@ACT-Europe.FR>, gdb@sources.redhat.com
Subject: Re: set processor command
Date: Fri, 01 Nov 2002 06:18:00 -0000 [thread overview]
Message-ID: <15810.35905.524789.755231@localhost.redhat.com> (raw)
In-Reply-To: <3DBFE816.4050801@redhat.com>
Andrew Cagney writes:
> > 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 ?
>
> The code was rationalied (across a number of architectures) and also
> made very generic. GDB ``supports'' any architecture/machine that is both:
>
> - known by bfd
> - known by gdb
>
> It's included in the list. The names are obtained via a query to BFD.
>
> A useful new feature (BFD and GDB) might be to also obtain a brief
> description of the architecture/machine.
Yes, but I think that the 5.2.1 version was only returning the rs6000
variants, which was a bug, and I think this was fixed when I did the
e500 support. The CVS head version of gdb returns the following now,
which is the correct set:
(gdb) set processor
Requires an argument. Valid arguments are rs6000:6000, rs6000:rs1, rs6000:rsc, rs6000:rs2, powerpc:common, powerpc:common64, powerpc:603, powerpc:EC603e, powerpc:604, powerpc:403, powerpc:601, powerpc:620, powerpc:630, powerpc:a35, powerpc:rs64ii, powerpc:rs64iii, powerpc:7400, powerpc:e500, powerpc:MPC8XX, auto.
Elena
>
> Andrew
>
prev parent reply other threads:[~2002-11-01 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 2:00 Romain Berrendonner
2002-10-30 6:09 ` Andrew Cagney
2002-11-01 6:18 ` Elena Zannoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15810.35905.524789.755231@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=ac131313@redhat.com \
--cc=berrendo@ACT-Europe.FR \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox