From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Implement support for PowerPC BookE ranged watchpoints
Date: Tue, 11 Jan 2011 21:09:00 -0000 [thread overview]
Message-ID: <1294775316.4102.17.camel@hactar> (raw)
In-Reply-To: <201101102336.24435.pedro@codesourcery.com>
On Mon, 2011-01-10 at 23:36 +0000, Pedro Alves wrote:
> On Monday 10 January 2011 19:17:38, Thiago Jung Bauermann wrote:
> > + the memory layout of a scalar type. E.g., an array or struct with only one
>
> Double space.
>
> > +static int
> > +resources_needed_watchpoint (const struct bp_location *bl)
> > +{
> > + int length = bl->owner->exact? 1 : bl->length;
> > +
> > + return target_region_ok_for_hw_watchpoint (bl->address, length);
> > }
>
> Indenting looks wrong. Otherwise okay to commit. Thanks for persevering!
Here's the patch I committed to fix the errors above.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
2010-01-11 Thiago Jung Bauermann <bauerman@br.ibm.com>
* breakpoint.c (resources_needed_watchpoint): Fix indentation.
* gdbtypes.c (is_scalar_type_recursive): Fix formatting.
Index: gdb.git/gdb/breakpoint.c
===================================================================
--- gdb.git.orig/gdb/breakpoint.c 2011-01-11 17:36:04.000000000 -0200
+++ gdb.git/gdb/breakpoint.c 2011-01-11 17:36:04.000000000 -0200
@@ -8278,9 +8278,9 @@ remove_watchpoint (struct bp_location *b
static int
resources_needed_watchpoint (const struct bp_location *bl)
{
- int length = bl->owner->exact? 1 : bl->length;
+ int length = bl->owner->exact? 1 : bl->length;
- return target_region_ok_for_hw_watchpoint (bl->address, length);
+ return target_region_ok_for_hw_watchpoint (bl->address, length);
}
/* The breakpoint_ops structure to be used in hardware watchpoints. */
Index: gdb.git/gdb/gdbtypes.c
===================================================================
--- gdb.git.orig/gdb/gdbtypes.c 2011-01-11 17:39:30.000000000 -0200
+++ gdb.git/gdb/gdbtypes.c 2011-01-11 17:39:38.000000000 -0200
@@ -1977,8 +1977,8 @@ is_scalar_type (struct type *type)
}
/* Return true if T is scalar, or a composite type which in practice has
- the memory layout of a scalar type. E.g., an array or struct with only one
- scalar element inside it, or a union with only scalar elements. */
+ the memory layout of a scalar type. E.g., an array or struct with only
+ one scalar element inside it, or a union with only scalar elements. */
int
is_scalar_type_recursive (struct type *t)
prev parent reply other threads:[~2011-01-11 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 19:18 Thiago Jung Bauermann
2011-01-10 23:36 ` Pedro Alves
2011-01-11 19:48 ` Thiago Jung Bauermann
2011-01-11 21:09 ` Thiago Jung Bauermann [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=1294775316.4102.17.camel@hactar \
--to=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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