From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>, toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH] sim: start a unified sim_do_command
Date: Wed, 22 Jun 2011 20:49:00 -0000 [thread overview]
Message-ID: <201106221648.56445.vapier@gentoo.org> (raw)
In-Reply-To: <201106221616.01999.vapier@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 1826 bytes --]
On Wednesday, June 22, 2011 16:16:00 Mike Frysinger wrote:
> On Wednesday, June 22, 2011 16:01:10 Tom Tromey wrote:
> > >>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
> > Mike> Since sim_do_command for many people simply calls sim_args_command,
> > start Mike> a unified version of it. For people who handle their own
> > options, they Mike> could switch to this by using sim_add_option_table
> > instead.
> >
> > I don't actually know anything about this code, but the patch seems to
> > remove implementations of sim_do_command that do more than dispatch to
> > sim_args_command.
>
> some arches didnt call sim_args_command(), now they do. bug fix for them.
>
> some arches would display an error message when users passed an old command
> option and inform them of the new one. i think people have had long enough
> for that migration, and they can pretty easily figure things out with the
> normal help output.
>
> m68hc11 provided a dedicated "info" to call an arch-specific
> sim_get_info(), but the common sim_info() entry point also calls that.
> m68hc11 would also rewrite its internal device tree when people changed
> files, but this behavior deviates from the standard sim behavior, so i
> dont think it should be there at all. the normal sim workflow
> (target;file;load) should continue to work.
>
> m32r provided a dedicated hook for reading two pseudo registers, but that
> should be done via the normal gdb interface rather than hooking the command
> line like this.
>
> i think that sums up all deviations.
if the m68hc11/m32r peeps really want to keep this behavior, i can rework the
Makefiles so that arches have to opt into the command. the idea though was to
make this a standard func so that new ports would get it automatically too.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-06-22 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1308516139-32225-1-git-send-email-vapier__28363.8018918738$1308516131$gmane$org@gentoo.org>
2011-06-22 20:01 ` Tom Tromey
2011-06-22 20:16 ` Mike Frysinger
2011-06-22 20:49 ` Mike Frysinger [this message]
[not found] ` <201106221648.56445.vapier__11186.3887090751$1308775772$gmane$org@gentoo.org>
2011-07-05 18:38 ` Tom Tromey
2011-06-19 20:41 Mike Frysinger
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=201106221648.56445.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=toolchain-devel@blackfin.uclinux.org \
--cc=tromey@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