From: Joel Brobecker <brobecker@adacore.com>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
gdb-patches@sourceware.org, Matt Tyrlik <tyrlik@us.ibm.com>
Subject: Re: [PATCH 3/4] Support ranged and masked watchpoints
Date: Tue, 12 Jan 2010 18:06:00 -0000 [thread overview]
Message-ID: <20100112180636.GO2007@adacore.com> (raw)
In-Reply-To: <1263297701.18167.7.camel@gargoyle>
> This would probably depend on the target vector facelift?
Yes and no - I don't think it would be fair to refuse the feature
just because the current code is not optimal. This is why we should
try to find a compromise, where we don't make things worse, if we can.
It's not clear to me how to best balance everything, hence the rather
lengthy emails... (and perhaps the baby steps! ;-).
--
Joel
prev parent reply other threads:[~2010-01-12 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 0:32 Thiago Jung Bauermann
2010-01-04 17:33 ` Thiago Jung Bauermann
2010-01-12 11:00 ` Joel Brobecker
2010-01-12 13:56 ` Luis Machado
2010-01-12 18:06 ` Joel Brobecker [this message]
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=20100112180636.GO2007@adacore.com \
--to=brobecker@adacore.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=tyrlik@us.ibm.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