Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Jeff Holcomb <jeffh@redhat.com>, Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA] fix gdb.base/remote.c and h8300
Date: Tue, 28 Aug 2001 16:28:00 -0000	[thread overview]
Message-ID: <1010828232808.ZM17691@ocotillo.lan> (raw)
In-Reply-To: <Pine.SOL.3.91.1010828161147.25088W-100000@taarna.cygnus.com>

On Aug 28,  4:16pm, Jeff Holcomb wrote:

> > On Aug 28, 11:12am, Jeff Holcomb wrote:
> > 
> > > +#ifdef __H8300__
> > > +# define RANDOM_DATA_SIZE (1024)
> > > +#endif
> > > +
> > 
> > We need to think of a better way to do this.  I've run into a similar
> > problem on a target that I've worked on in the past too.  I don't think
> > that adding ifdefs for all the targets that need a smaller size is the
> > way to go...
> 
> Yes.  I agree there needs to be a better way.  The problem I have is that 
> the H8300s has 16-bit int and 16-bit pointers.  There's no way the large 
> structure defined in remote.c can fit so gcc spews a bunch of errors when 
> compiling.  There existed a mechanism already in remote.c to handle this, 
> so I just extended it to the h8300.
> 
> Whatever the solution, it has to be done in the preprocessor.  Perhaps 
> checking to see how big MAXINT is defined to be?

Yeah.  Or maybe just check sizeof (int)?

#if sizeof (int) <= 2
# define RANDOM_DATA_SIZE (1024)
#else
...
#endif

(That way we're not depending on any header files for this test.)


  reply	other threads:[~2001-08-28 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-28 11:12 Jeff Holcomb
2001-08-28 12:33 ` Kevin Buettner
2001-08-28 16:17   ` Jeff Holcomb
2001-08-28 16:28     ` Kevin Buettner [this message]
2001-08-28 17:14       ` Andrew Cagney
2001-08-28 18:41         ` Kevin Buettner
2001-08-28 16:29     ` Andrew Cagney
2001-08-28 15:20 ` Michael Snyder

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=1010828232808.ZM17691@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=jeffh@redhat.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