From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/7] Support reading/writing memory on architectures with non 8-bits bytes
Date: Thu, 09 Apr 2015 08:20:00 -0000 [thread overview]
Message-ID: <83d23dg1bd.fsf@gnu.org> (raw)
In-Reply-To: <1428522979-28709-1-git-send-email-simon.marchi@ericsson.com>
> From: Simon Marchi <simon.marchi@ericsson.com>
> CC: Simon Marchi <simon.marchi@ericsson.com>
> Date: Wed, 8 Apr 2015 15:56:12 -0400
>
> On such a system, memory is addressable in atomic chunks of 16-bits. On
> a "normal" system, you have 8 bits of data associated with each memory
> address:
>
> Address Data
> ---------------
> 0x1000 0xaa
> 0x1001 0xbb
> 0x1002 0xcc
> 0x1003 0xdd
>
> whereas on a system with 16-bits bytes, you have 16-bits of data per
> address:
>
> Address Data
> ---------------
> 0x1000 0xaaaa
> 0x1001 0xbbbb
> 0x1002 0xcccc
> 0x1003 0xdddd
>
> To support these systems, GDB must be modified to consider the byte size
> when reading/writing memory. This is what this first patch series is
> about.
>
> Also, on these systems, sizeof(char) == 1 == 16 bits. There is therefore
> many places related to types and values handling that need to be
> modified. This will be the subject of subsequent patch series.
I wonder: wouldn't it be possible to keep the current "byte == 8 bits"
notion, and instead to change the way addresses are interpreted by the
target back-end?
IOW, do we really need to expose this issue all the way to the higher
levels of GDB application code?
next prev parent reply other threads:[~2015-04-09 8:20 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 6/7] remote: 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 5/7] target: consider byte size when reading/writing memory Simon Marchi
2015-04-08 19:56 ` [PATCH 7/7] MI: Consider " 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 1/7] Various cleanups in target read/write code Simon Marchi
2015-04-09 8:20 ` Eli Zaretskii [this message]
2015-04-09 15:39 ` [PATCH 0/7] Support reading/writing memory on architectures with non 8-bits bytes 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
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=83d23dg1bd.fsf@gnu.org \
--to=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