Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Eliminate TARGET_HAS_HARDWARE_WATCHPOINTS
Date: Mon, 13 Sep 2004 20:48:00 -0000	[thread overview]
Message-ID: <4146070D.3040104@gnu.org> (raw)
In-Reply-To: <01c499c9$Blat.v2.2.2$deebfb60@zahav.net.il>

>>Date: Mon, 13 Sep 2004 10:27:59 -0400
>>> From: Andrew Cagney <cagney@gnu.org>
>>> Cc: drow@false.org, gdb-patches@sources.redhat.com
>>> 
>>> I've committed this part of my change:
> 
> 
> Great!  So you've gone out and committed a patch over an objection of
> a core maintainer who worked quite a bit on the releated code.

No.  The changes that in anyway formalize the deprecation of all this:

cagney@nettle$ frep TARGET_HAS_HARDWARE_WATCHPOINTS
config/i386/nm-i386sco5.h:56:#define TARGET_HAS_HARDWARE_WATCHPOINTS
config/i386/nm-i386sol2.h:25:#define TARGET_HAS_HARDWARE_WATCHPOINTS
config/mips/nm-irix5.h:25:#define TARGET_HAS_HARDWARE_WATCHPOINTS
config/sparc/nm-sol2.h:36:#define TARGET_HAS_HARDWARE_WATCHPOINTS
doc/gdbint.texinfo:403:@findex TARGET_HAS_HARDWARE_WATCHPOINTS
doc/gdbint.texinfo:404:@item TARGET_HAS_HARDWARE_WATCHPOINTS
doc/gdbint.texinfo:3836:@item TARGET_HAS_HARDWARE_WATCHPOINTS
i386v-nat.c:45:#ifdef TARGET_HAS_HARDWARE_WATCHPOINTS
i386v-nat.c:107:#ifdef TARGET_HAS_HARDWARE_WATCHPOINTS
i386v-nat.c:273:#endif /* TARGET_HAS_HARDWARE_WATCHPOINTS */
procfs.c:2878:#if !defined (TARGET_HAS_HARDWARE_WATCHPOINTS)
procfs.c:5282:#ifndef TARGET_HAS_HARDWARE_WATCHPOINTS

and that you have so stridently objected to, are still all sitting on 
the table.

Andrew



  reply	other threads:[~2004-09-13 20:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 13:59 Andrew Cagney
2004-09-06  5:03 ` Eli Zaretskii
2004-09-06 14:05   ` Andrew Cagney
2004-09-06 18:47     ` Eli Zaretskii
2004-09-07 21:20       ` Andrew Cagney
2004-09-08  3:51         ` Eli Zaretskii
2004-09-08 14:28           ` Andrew Cagney
2004-09-08 15:18             ` Eli Zaretskii
2004-09-08 15:23               ` Daniel Jacobowitz
2004-09-09  3:41                 ` Eli Zaretskii
2004-09-09  3:53                   ` Daniel Jacobowitz
2004-09-09  4:04                     ` Eli Zaretskii
2004-09-09 12:47                       ` Daniel Jacobowitz
2004-09-09 18:52                         ` Eli Zaretskii
2004-09-12 16:33                           ` Andrew Cagney
2004-09-12 18:42                             ` Eli Zaretskii
2004-09-13 14:30                               ` Andrew Cagney
2004-09-13 19:43                                 ` Eli Zaretskii
2004-09-13 20:48                                   ` Andrew Cagney [this message]
2004-09-15  7:20                                     ` Eli Zaretskii
2004-09-15 16:11                                       ` Andrew Cagney
2004-09-16 10:53                                         ` 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=4146070D.3040104@gnu.org \
    --to=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --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