From: Jeff Holcomb <jeffh@redhat.com>
To: gdb-patches@sourceware.cygnus.com
Subject: [PATCH] fix gdb.base/remote.c for small int targets
Date: Mon, 03 Sep 2001 12:55:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010903125442.25088R-100000@taarna.cygnus.com> (raw)
In-Reply-To: <Pine.SOL.3.91.1010830220552.25088t-100000@taarna.cygnus.com>
Committed.
On Thu, 30 Aug 2001, Jeff Holcomb wrote:
> 2001-08-30 Jeff Holcomb <jeffh@redhat.com>
>
> * gdb.base/remote.c: Use a small buffer for targets with 16-bit
> ints.
>
> Index: remote.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/remote.c,v
> retrieving revision 1.2
> diff -u -p -r1.2 remote.c
> --- remote.c 2001/07/17 21:47:19 1.2
> +++ remote.c 2001/08/31 05:05:33
> @@ -23,16 +23,16 @@ BEGIN {
>
> */
>
> -#ifdef mc68hc11
> +#include <limits.h>
> +/* For targets with 16bit int, use a 1k buffer. */
> +#if INT_MAX < 32768
> # define RANDOM_DATA_SIZE (1024)
> -#endif
> -
> +#else
> /* Use a character buffer to avoid byte order problems. 48k is
> chosen so that the buffer required at least 3 16k packets but
> targets often have no more than 64k of data. */
> /* If you change this data, you will also have to change the checks
> for the data in remote.c */
> -#ifndef RANDOM_DATA_SIZE
> # define RANDOM_DATA_SIZE (3 * 2048 * 8)
> # define BIG_RANDOM_DATA
> #endif
prev parent reply other threads:[~2001-09-03 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B8EFA12.2010403@cygnus.com>
2001-08-30 22:11 ` [RFA] " Jeff Holcomb
2001-08-31 0:27 ` Eli Zaretskii
2001-08-31 8:29 ` Kevin Buettner
2001-08-31 9:01 ` Eli Zaretskii
2001-08-31 9:45 ` Kevin Buettner
2001-08-31 11:22 ` Eli Zaretskii
2001-08-31 8:30 ` Kevin Buettner
2001-09-03 12:55 ` Jeff Holcomb [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=Pine.SOL.3.91.1010903125442.25088R-100000@taarna.cygnus.com \
--to=jeffh@redhat.com \
--cc=gdb-patches@sourceware.cygnus.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