From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>,
Sergio Durigan <sdurigan@redhat.com>
Subject: Re: Splint report and scripts for gdb (was: Expand bitpos and type.length)
Date: Mon, 02 Jul 2012 02:49:00 -0000 [thread overview]
Message-ID: <20120702081923.5a5322d4@spoyarek> (raw)
In-Reply-To: <20120701193755.GA8904@host2.jankratochvil.net>
On Sun, 1 Jul 2012 21:37:55 +0200, Jan wrote:
> While you now consider it as two different records. But this should
> not miss any record, it just adds more records to process - although
> you discard these in splint-siddhesh-process-locdiff by rules like so
> it does not matter: if (/Previous definition of \w+: \w+/) {
> Not sure if it was all intentional or not.
It was intentional, because the extra spaces are also used in cases
where there are two warnings for one line.
> # If the TYPE_LENGTH expression is a builtin_type then we're
> safe. $_ = $expr;
> return 1 if (/builtin_type[^ ]+->length/);
> - I would not call it safe, it can be a part of an arbitrary large
> expression. But the 6 cases where it applies are OK.
Yes, this was hard-coding on my part based on the input.
> if (/^ (Right)|(Left) operand of \W+ /) {
> - it did not discard any important line but the regex is dangerously
> wrong, it does:
> if (/^ Right/ || /Left operand of \W+ /) {
This should have been:
if (/^ ((Right)|(Left)) operand of \W+ /) {
>
> Otherwise I have made comments to your .report file. I believe we
> should follow now the 'compact' form instead. It is a lot of work as
> I see.
Thanks, that was the report before I did further work on the script.
I'll work on the rest and post the report with the compact form next.
Regards,
Siddhesh
prev parent reply other threads:[~2012-07-02 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 13:18 Siddhesh Poyarekar
2012-07-01 19:38 ` Jan Kratochvil
2012-07-02 2:49 ` Siddhesh Poyarekar [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=20120702081923.5a5322d4@spoyarek \
--to=siddhesh@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=sdurigan@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