From: Eli Zaretskii <eliz@delorie.com>
To: dje@transmeta.com
Cc: taylor@cygnus.com, gdb@sources.redhat.com
Subject: Re: harvard architectures - the d10v
Date: Fri, 09 Feb 2001 00:25:00 -0000 [thread overview]
Message-ID: <200102090825.DAA23231@indy.delorie.com> (raw)
In-Reply-To: <14979.4102.901998.291182@casey.transmeta.com>
> From: Doug Evans <dje@transmeta.com>
> Date: Thu, 8 Feb 2001 13:30:46 -0800 (PST)
>
> Agreed. The way I would extend this is to name the address space
> you want the address to refer to. Without claiming this is
> the best syntax/wording/etc., maybe something like
>
> x/x insn:0x12345678
> x/i insn:0x12345678
> x/x data:0x12345678
> x/i data:0x12345678
>
> - there could be a default address space,
> or target could specify that "x/x 0x12345678 is an error
> - users of targets without address spaces would see no change
> - I would treat the address space names as target specific
>
> Implementation-wise, this would get translated to a CORE_ADDR
> that had two parts: address space id, and address.
Are we introducing segments into GDB? Because if we are, I can think
about a few more possible applications, for x86 for example.
next parent reply other threads:[~2001-02-09 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200102082037.PAA07784@texas.cygnus.com>
[not found] ` <14979.4102.901998.291182@casey.transmeta.com>
2001-02-09 0:25 ` Eli Zaretskii [this message]
2001-02-09 7:32 David Taylor
-- strict thread matches above, loose matches on Subject: below --
2001-02-08 11:52 Andrew Cagney
[not found] ` <14979.2615.608456.807316@casey.transmeta.com>
[not found] ` <3A831746.CAB9C621@cygnus.com>
2001-02-08 23:59 ` Doug Evans
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=200102090825.DAA23231@indy.delorie.com \
--to=eliz@delorie.com \
--cc=dje@transmeta.com \
--cc=gdb@sources.redhat.com \
--cc=taylor@cygnus.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