From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Siddhesh Poyarekar <siddhesh@redhat.com>, gdb-patches@sourceware.org
Subject: Re: bitpos expansion patches summary
Date: Tue, 11 Sep 2012 19:37:00 -0000 [thread overview]
Message-ID: <20120911193730.GA27448@host2.jankratochvil.net> (raw)
In-Reply-To: <87r4q88ipd.fsf@fleche.redhat.com>
On Tue, 11 Sep 2012 21:26:06 +0200, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> Jan> Additionally I am pretty sure the codebase will get broken soon
> Jan> again as it is common GDB practice to use 'int' for every length
> Jan> and I do not review very every check-in. So it would be nice to
> Jan> possibly be able to do such incremental re-checks in the future;
> Jan> although I am not sure it will be done.
>
> Perhaps you could post something here describing your intended rules.
Yes, I will try to make some summary for further reviews.
> It could be part of patch review. That obviously won't catch
> everything, but we can make an effort at least.
Yes, it should be.
> Jan> Also IMO (any feedback from other maintainers?) we need full
> Jan> annotation of the patch file as with such large number of change
> Jan> there is not clear which changes are justified and whether there
> Jan> are no excessive changes.
> Jan> http://people.redhat.com/jkratoch/bitpos3.patch
> Jan> (lines starting with 'x')
>
> Ouch, 168 hits.
>
> I guess I'm not really sure what you mean by a full annotation.
$ wget -q -O - http://people.redhat.com/jkratoch/bitpos3.patch|perl -lne '$pn=/^[+](?![+][+] )/;(/^x/?$done:$missing)++ if $p&&!$pn;$p=$pn;END{print "done=$done,missing=$missing";}'
done=120,missing=574
I have annotated 120 changes but still 574 changes need to be annotated.
(A few of them were commented by a suggestion for their removal etc.)
This case I call 'done', annotated:
/* Append a trace_quick instruction to EXPR, to record N bytes. */
-extern void ax_trace_quick (struct agent_expr *EXPR, int N);
+extern void ax_trace_quick (struct agent_expr *EXPR, LONGEST N);
xFIXED(Expand N to LONGEST): (ax-gdb.c:516): FUNC(ax_trace_quick): (ULONGEST to int) [(type)->length]
This case I call 'missing', not yet annotated:
long reg_r0, reg_r1, reg_r2;
- int total_len = 0;
+ LONGEST total_len = 0;
enum bfin_abi abi = bfin_abi (gdbarch);
Thanks,
Jan
next prev parent reply other threads:[~2012-09-11 19:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 19:24 Siddhesh Poyarekar
2012-08-07 14:39 ` Jan Kratochvil
2012-08-07 15:10 ` Siddhesh Poyarekar
2012-08-07 15:48 ` Siddhesh Poyarekar
2012-08-08 22:43 ` Jan Kratochvil
2012-08-08 22:50 ` Jan Kratochvil
2012-08-09 2:04 ` Siddhesh Poyarekar
2012-08-10 1:28 ` Siddhesh Poyarekar
2012-08-17 9:35 ` Siddhesh Poyarekar
2012-08-09 20:04 ` Jan Kratochvil
2012-08-10 1:44 ` Siddhesh Poyarekar
2012-08-10 7:51 ` Jan Kratochvil
2012-08-10 7:58 ` Siddhesh Poyarekar
2012-08-12 17:57 ` Jan Kratochvil
2012-08-13 2:52 ` Siddhesh Poyarekar
2012-08-13 13:49 ` Jan Kratochvil
2012-08-13 14:04 ` Siddhesh Poyarekar
2012-08-13 14:12 ` Jan Kratochvil
2012-08-13 14:24 ` Siddhesh Poyarekar
2012-08-17 9:35 ` [PATCH 4/3] bitpos: Expand parameters of watchpoint functions Siddhesh Poyarekar
2012-08-19 16:42 ` bitpos expansion patches summary Jan Kratochvil
2012-08-21 6:51 ` Siddhesh Poyarekar
2012-08-26 18:21 ` Jan Kratochvil
2012-08-27 8:10 ` Siddhesh Poyarekar
2012-08-27 14:02 ` Jan Kratochvil
2012-09-02 18:15 ` Jan Kratochvil
2012-09-07 10:52 ` Siddhesh Poyarekar
2012-09-11 19:04 ` Jan Kratochvil
2012-09-11 19:26 ` Tom Tromey
2012-09-11 19:37 ` Jan Kratochvil [this message]
2012-09-13 18:45 ` Jan Kratochvil
2012-09-13 16:48 ` Jan Kratochvil
2012-09-14 6:20 ` Siddhesh Poyarekar
2012-09-04 15:03 ` Jan Kratochvil
2012-09-04 15:09 ` Siddhesh Poyarekar
2012-09-07 11:10 ` Siddhesh Poyarekar
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=20120911193730.GA27448@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=siddhesh@redhat.com \
--cc=tromey@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