From: <Paul_Koning@Dell.com>
To: <simon.marchi@ericsson.com>
Cc: <eliz@gnu.org>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Document non-8-bits-addressable support in NEWS
Date: Thu, 27 Aug 2015 14:11:00 -0000 [thread overview]
Message-ID: <0380352E-1706-4A29-BE38-D888F6B969E6@dell.com> (raw)
In-Reply-To: <55DF11C2.6020303@ericsson.com>
> On Aug 27, 2015, at 9:33 AM, Simon Marchi <simon.marchi@ericsson.com> wrote:
>
> On 15-08-26 10:37 PM, Eli Zaretskii wrote:
>> I think you should drop the second sentence, as it doesn't add any
>> useful information and is slightly inaccurate. I think everyone will
>> understand what non-8-bits-addressable means.
>
> Right, thanks. Pushed with second sentence removed.
>
>
> From fd2ae5d6a3a5c4007be45f9b2f325955ac316f36 Mon Sep 17 00:00:00 2001
> From: Simon Marchi <simon.marchi@ericsson.com>
> Date: Thu, 27 Aug 2015 09:30:00 -0400
> Subject: [PATCH] Document non-8-bits addressable memory support in NEWS
>
> I think it would be a good idea to document that gdb now has (basic)
> support to read/write memory on architectures with non-8-bits memory.
> Hopefully somebody will see it and say "Hey! We can now (more easily)
> port GDB to our strange DSP that has 32-bits-addressable memory!" and do
> it.
Would it make sense to say what it can handle? Multiples of 8? Powers of 2? Any number?
"Any number" (like 27, or 60) is probably found only in historic machines, but I remember DSPs with 24 bit memory.
paul
next prev parent reply other threads:[~2015-08-27 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 20:17 Simon Marchi
2015-08-27 2:38 ` Eli Zaretskii
2015-08-27 13:34 ` Simon Marchi
2015-08-27 14:11 ` Paul_Koning [this message]
2015-08-27 14:26 ` Simon Marchi
2015-08-27 15:05 ` Simon Marchi
2015-08-27 15:13 ` Paul_Koning
2015-08-27 15:39 ` Eli Zaretskii
2015-08-28 19:37 ` Simon Marchi
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=0380352E-1706-4A29-BE38-D888F6B969E6@dell.com \
--to=paul_koning@dell.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