Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Dave Brolley <brolley@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] New Target - Fujitsu FRV
Date: Thu, 20 Jun 2002 20:31:00 -0000	[thread overview]
Message-ID: <3D129E05.5080504@cygnus.com> (raw)
In-Reply-To: <3D079928.50303@redhat.com>

> +/*#define HAVE_STEPPABLE_WATCHPOINT 1*/
> +
> +#define STOPPED_BY_WATCHPOINT(W) \
> +   ((W).kind == TARGET_WAITKIND_STOPPED \
> +   && (W).value.sig == TARGET_SIGNAL_TRAP \
> +   && (frv_stopped_data_address() != ((CORE_ADDR)0)))
> +extern CORE_ADDR frv_stopped_data_address(void);
> +
> +/* Use these macros for watchpoint insertion/deletion.  */
> +#define target_insert_watchpoint(addr, len, type) \
> +		remote_insert_watchpoint (addr, len, type)
> +#define target_remove_watchpoint(addr, len, type) \
> +		remote_remove_watchpoint (addr, len, type)
> +#define target_insert_hw_breakpoint(addr, shadow) \
> +		remote_insert_hw_breakpoint (addr, 1)
> +#define target_remove_hw_breakpoint(addr, shadow) \
> +		remote_remove_hw_breakpoint (addr, 1)
> +#define target_stopped_data_address() frv_stopped_data_address()
> +
> +/* These declarations should be in remote.h, no?  */
> +extern int remote_insert_watchpoint (CORE_ADDR addr, int len, int type);
> +extern int remote_remove_watchpoint (CORE_ADDR addr, int len, int type);
> +extern int remote_insert_hw_breakpoint (CORE_ADDR addr, int len);
> +extern int remote_remove_hw_breakpoint (CORE_ADDR addr, int len);

Sigh! Another target and still the hardware breakpoint problem isn't 
fixed.  I did some digging and I note you are not the author here :-)

> +SIM_OBS = remote-sim.o
> +SIM = ../sim/frv/libsim.a

For the moment leave these out, but otherwize approved.

Once committed, can you please check 
http://sources.redhat.com/gdb/current/ari/ for anything identifed (at 
the page top) from these new files.

Can you also try building with --enable-gdb-build-warnings=,-Werror.

Fixes related to both of these are considered obvious.

enjoy,
Andrew



  parent reply	other threads:[~2002-06-21  3:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12 11:55 Dave Brolley
2002-06-20 20:25 ` Andrew Cagney
2002-06-21 13:27   ` Dave Brolley
2002-06-21 13:37     ` MAINTAINERS patch; Was: " Andrew Cagney
2002-06-20 20:31 ` Andrew Cagney [this message]
2002-06-21 14:36   ` Dave Brolley
2002-06-21 14:48     ` Andrew Cagney
2002-06-12 12:31 Dave Brolley

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=3D129E05.5080504@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=brolley@redhat.com \
    --cc=gdb-patches@sources.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