From: Daniel Jacobowitz <drow@false.org>
To: Robin den Hertog <robin@den-hertog.org>
Cc: gdb@sourceware.org
Subject: Re: byte word and int(32) safe memory access?
Date: Fri, 22 Aug 2008 14:43:00 -0000 [thread overview]
Message-ID: <20080822134134.GA16468@caradoc.them.org> (raw)
In-Reply-To: <1021db0c0808220616x1c967d1eh4b46027c6021052f@mail.gmail.com>
On Fri, Aug 22, 2008 at 03:16:48PM +0200, Robin den Hertog wrote:
> the documentation and code of gdb lead me to believe the only time you
> read memory larger than a byte at once is for speed optimization.
> but you're saying that is i request an address with the length at 2
> bytes it will always be read in ONE read action ($m40,2#xx)?
> or
> does it depend on the address size?
> "even if addr is word-aligned and length is a multiple of the word
> size, the stub is free to use byte accesses"
> I figured that meant even $m00004040,4#xx and any length above that
> (but still dividable by 4) you would still be unsure how it is read.
>
> changing the stub could still mean that as soon as you connect a
> different fpga (to the same cpu) you have to rewrite your stub ?.
In practice GDB will never do byte accesses if you ask for a word.
What your stub does with them is up to the stub. But you're in
control of the stub, presumably?
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-08-22 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 14:30 Robin den Hertog
2008-08-22 14:32 ` Daniel Jacobowitz
2008-08-22 14:34 ` Robin den Hertog
2008-08-22 14:43 ` Daniel Jacobowitz [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=20080822134134.GA16468@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=robin@den-hertog.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