From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: gdb@sources.redhat.com
Subject: Re: nm.h, *-nat.c and multi-arch?
Date: Wed, 04 Jul 2001 10:28:00 -0000 [thread overview]
Message-ID: <7263-Wed04Jul2001202553+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3B43404E.6090805@cygnus.com>
> Date: Wed, 04 Jul 2001 12:11:58 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
>
> o customize to enable
> extra (OS/arch specific?) features.
> (The i386 hw breakpoint code
> comes to mind.)
>
> Here again, I think this should really
> be host independant.
I don't think it's possible, based on many hours of staring at the
various implementations of hw breakpoints. The differences are not
always major, but IMHO significant enough to render any attempt to
unify them be a huge effort with a very small benefit.
Even IA64 is sufficiently different from IA32 so as to prevent any
reasonable attempt to unify the code which handles watchpoints.
next prev parent reply other threads:[~2001-07-04 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 9:12 Andrew Cagney
2001-07-04 10:28 ` Eli Zaretskii [this message]
2001-07-04 11:36 ` Andrew Cagney
2001-07-04 11:54 ` Eli Zaretskii
2001-07-04 10:43 ` Daniel Jacobowitz
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=7263-Wed04Jul2001202553+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=gdb@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