From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: gdb@sourceware.org
Subject: Re: Address spaces
Date: Fri, 25 Jul 2008 08:50:00 -0000 [thread overview]
Message-ID: <1216972801.3530.218.camel@thomas> (raw)
In-Reply-To: <e394668d0807241116i520b01e2t92070e7f282ba83c@mail.gmail.com>
>>> Doug Evans wrote:
>>>
>>> Do you have some specific ideas in mind? Because I was assuming (and this
>>> is good to be aware of) that there would not be more than one address space
>>> associated with a process. (Instantly split I/D targets a la D10V come to
>>> mind, although that was handled by distinguishing pointers from addresses.)
This would be useful for architectures which have large numbers of
configuration registers. These are not always mapped in the main address
space. They could conveniently be represented in a separate address
space. Examples include the OpenCores OpenRISC 1000 special purpose
registers and the ARC 600/700 auxiliary address space.
Jeremy Bennett
--
Tel: +44 (1202) 416955
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com
next prev parent reply other threads:[~2008-07-25 8:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 0:14 Stan Shebs
2008-07-24 0:30 ` Doug Evans
2008-07-24 6:15 ` Stan Shebs
2008-07-24 15:56 ` Ulrich Weigand
2008-07-24 18:17 ` Stan Shebs
2008-07-24 18:28 ` Doug Evans
2008-07-25 5:52 ` Michael Snyder
2008-07-25 8:50 ` Jeremy Bennett [this message]
2008-07-24 20:31 ` Ulrich Weigand
2008-07-25 18:50 ` Stan Shebs
2008-07-25 3:31 ` Michael Snyder
2008-07-24 21:49 ` Paul Pluzhnikov
2008-07-25 3:29 ` Michael Snyder
2008-07-25 18:32 ` Stan Shebs
2008-07-25 19:13 ` Mark Kettenis
2008-07-25 19:24 ` Stan Shebs
2008-07-31 18:43 ` Andrew Cagney
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=1216972801.3530.218.camel@thomas \
--to=jeremy.bennett@embecosm.com \
--cc=gdb@sourceware.org \
/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