From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/7] Support reading/writing memory on architectures with non 8-bits bytes
Date: Fri, 10 Apr 2015 16:35:00 -0000 [thread overview]
Message-ID: <5527FBD6.4090809@redhat.com> (raw)
In-Reply-To: <5527F3BC.3030005@ericsson.com>
On 04/10/2015 05:01 PM, Simon Marchi wrote:
> The term we are looking for is one for a single memory unit, regardless of its size.
That suggests "addressable memory unit".
Looks like http://en.wikipedia.org/wiki/Word_%28computer_architecture%29 calls
it "Unit of address resolution".
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-04-10 16:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 19:56 Simon Marchi
2015-04-08 19:56 ` [PATCH 1/7] Various cleanups in target read/write code Simon Marchi
2015-04-08 19:56 ` [PATCH 7/7] MI: Consider byte size when reading/writing memory Simon Marchi
2015-04-08 19:56 ` [PATCH 3/7] Clarify doc about memory read/write and non-8-bits bytes Simon Marchi
2015-04-09 7:02 ` Eli Zaretskii
2015-04-08 19:56 ` [PATCH 5/7] target: consider byte size when reading/writing memory Simon Marchi
2015-04-08 19:56 ` [PATCH 2/7] Cleanup some docs about memory write Simon Marchi
2015-04-08 19:56 ` [PATCH 4/7] gdbarch: add memory_byte_size method Simon Marchi
2015-04-08 19:56 ` [PATCH 6/7] remote: Consider byte size when reading/writing memory Simon Marchi
2015-04-09 8:20 ` [PATCH 0/7] Support reading/writing memory on architectures with non 8-bits bytes Eli Zaretskii
2015-04-09 15:39 ` Simon Marchi
2015-04-09 16:29 ` Eli Zaretskii
2015-04-09 21:00 ` Simon Marchi
2015-04-10 8:11 ` Eli Zaretskii
2015-04-10 16:01 ` Simon Marchi
2015-04-10 16:35 ` Pedro Alves [this message]
2015-04-10 16:39 ` Paul_Koning
2015-04-10 17:34 ` Simon Marchi
2015-04-10 17:42 ` Eli Zaretskii
2015-04-10 18:01 ` Simon Marchi
2015-04-10 18:16 ` Eli Zaretskii
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=5527FBD6.4090809@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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