Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@wins.uva.nl>
To: eliz@is.elta.co.il
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Cleanup i386-tdep.c
Date: Mon, 19 Feb 2001 08:03:00 -0000	[thread overview]
Message-ID: <200102191602.f1JG2f622103@debye.wins.uva.nl> (raw)
In-Reply-To: <4331-Sun18Feb2001223249+0200-eliz@is.elta.co.il>

   Date: Sun, 18 Feb 2001 22:32:49 +0200
   From: "Eli Zaretskii" <eliz@is.elta.co.il>

   > Date: Sun, 18 Feb 2001 11:17:48 +0100
   > From: Mark Kettenis <kettenis@wins.uva.nl>
   > 
   > Please create i386-nat.c (and i386-nat.h, for the exported
   > interfaces).

   Is it okay to use preprocessor symbols, like i386-tdep.c does, to get
   the watchpoint code included only in those x86 ports which support
   this kind of watchpoints?  I mean, i386-nat.c, once created, will
   probably be added to NATDEPFILES of every native x86 platform, right?
   However, some of them might not support watchpoints through debug
   registers (I think Solaris doesn't).

In principle, I think we don't want to introduce any additional
preprocessor symbols if we can avoid it.  Since we only include
i386-nat.c in NATDEPFILES for configurations that actually use code
from that file, we don't need them yet.  If we ever add more code to
i386-nat.c and we want to elide the unused debug register code, we can
always introduce a preprocessor symbol at that moment.

Mark


  parent reply	other threads:[~2001-02-19  8:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-16 15:06 Mark Kettenis
2001-02-17 22:23 ` Eli Zaretskii
2001-02-18  2:17   ` Mark Kettenis
2001-02-18  3:07     ` Eli Zaretskii
2001-02-18 12:34     ` Eli Zaretskii
     [not found]     ` <4331-Sun18Feb2001223249+0200-eliz@is.elta.co.il>
2001-02-19  8:03       ` Mark Kettenis [this message]
2001-02-19 10:47     ` Andrew Cagney
2001-02-19 14:03       ` Mark Kettenis
2001-02-19 14:46         ` Fernando Nasser
2001-03-17 14:31 [PATCH]: " Mark Kettenis

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=200102191602.f1JG2f622103@debye.wins.uva.nl \
    --to=kettenis@wins.uva.nl \
    --cc=eliz@is.elta.co.il \
    --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