Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: <Paul_Koning@Dell.com>
Cc: <eliz@gnu.org>, <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 17:34:00 -0000	[thread overview]
Message-ID: <55280987.5060107@ericsson.com> (raw)
In-Reply-To: <1476603C-A0AA-42D4-B432-CDCF06901AF4@dell.com>

>> I understand your concern.  The term "byte" is probably set in stone as 8-bits for pretty
>> much everybody, so trying to redefine it as variable length would probably cause more harm
>> than good.
> 
> But if you work on several platforms, you would reasonably be expected to understand each of them.  Debugging on A, B, and C with a working knowledge only of A isn’t very realistic.
>
> 8 bits == byte is certainly the predominant modern usage, but it hasn’t always been that way and even today it apparently isn’t quite universal.  GCC used to support architectures that did not do 8-bit byte memory addressing, though that capability seems to have faded away in the past couple of years.

I guess you are referring to older architectures with 6, 7, 9, 12, 36-bits or other
byte size.  I'd like to make it clear that our goal is not to support that kind of
bytes that is not a multiple of 8 bits.  That would be incredibly more complicated.


  reply	other threads:[~2015-04-10 17:34 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 4/7] gdbarch: add memory_byte_size method Simon Marchi
2015-04-08 19:56 ` [PATCH 2/7] Cleanup some docs about memory write 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 1/7] Various cleanups in target read/write code 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 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 7/7] MI: 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
2015-04-10 16:39             ` Paul_Koning
2015-04-10 17:34               ` Simon Marchi [this message]
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=55280987.5060107@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=Paul_Koning@Dell.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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