From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] bitpos expansion summary reloaded
Date: Wed, 03 Oct 2012 19:56:00 -0000 [thread overview]
Message-ID: <20121003195627.GA17283@host2.jankratochvil.net> (raw)
In-Reply-To: <20121003184155.03dceed4@spoyarek>
On Wed, 03 Oct 2012 15:11:55 +0200, Siddhesh Poyarekar wrote:
[...]
> make 2> build-warnings.out
Probably only in gdb/ directory otherwise it would create more needless output
to deal with.
[...]
> I then processed the two files with this wonderful looking command:
>
> diff -u build-master.out build-bitpos.out |
> perl -e 'while(<>){s{^(.)(.*)}{print "$2$1\n"}egm}' | sort |
> perl -e 'while(<>){s{^([^\]]+\])(.)$}{print "$2$1\n"}egm}' |
> grep "^[-+]" | ./checkreport2.pl | grep -v "^----" |
> grep -v "^+++" | grep "^+" |
> perl -e \
> 'while(<>){s{^([^\/]+/)+([^:]+:[^:]+):.*}{print "$2\n"}egm}' |
> while read loc; do
> grep -q "$loc" splint-bitpos3.locdiff.processed
This 'grep' has too relaxed search string, for example warnings in "main.c"
(there are some 'conversion' warnings) will match _29_ other files creating
false FOUND lines and therefore fogetting about possibly valid type safety
conversion problems.
There should be sure some fgrep -q "($loc:" or so.
Thanks,
Jan
break-interp-main.c
dmsym_main.c
dw2-cp-infcall-ref-static-main.c
dw2-entry-value-main.c
dw2-inline-param-main.c
dw2-noloc-main.c
dw2-param-error-main.c
dw2-ref-missing-frame-main.c
dw2-unresolved-main.c
gcore-relro-main.c
gdb1555-main.c
jit-dlmain.c
jit-main.c
main.c
mi-main.c
mips16-thunks-inmain.c
mips16-thunks-main.c
mips16-thunks-sinmain.c
print-file-var-main.c
shmain.c
skip-solib-main.c
solib-display-main.c
solib-list-main.c
solib-main.c
solib-overlap-main.c
solib-symbol-main.c
tls-main.c
tls-var-main.c
type-opaque-main.c
next prev parent reply other threads:[~2012-10-03 19:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 13:33 Siddhesh Poyarekar
2012-09-28 11:20 ` Jan Kratochvil
2012-09-28 11:40 ` Siddhesh Poyarekar
2012-09-28 12:06 ` Jan Kratochvil
2012-09-28 12:19 ` Siddhesh Poyarekar
2012-09-29 17:39 ` Jan Kratochvil
2012-09-29 18:12 ` Jan Kratochvil
2012-09-30 6:52 ` Jan Kratochvil
2012-10-01 5:21 ` Siddhesh Poyarekar
2012-10-01 6:14 ` Jan Kratochvil
2012-10-03 13:12 ` Siddhesh Poyarekar
2012-10-03 18:38 ` Jan Kratochvil
2012-10-04 7:20 ` Siddhesh Poyarekar
2012-10-03 19:56 ` Jan Kratochvil [this message]
2012-10-04 7:13 ` Jan Kratochvil
2012-10-21 7:36 ` Siddhesh Poyarekar
2012-10-22 20:45 ` Tom Tromey
2012-10-23 1:34 ` Jan Kratochvil
2012-10-23 1:58 ` Jan Kratochvil
2012-10-23 2:29 ` Siddhesh Poyarekar
2012-10-23 2:37 ` Jan Kratochvil
2012-10-23 2:38 ` Tom Tromey
2012-10-23 19:11 ` Jan Kratochvil
2012-10-24 18:33 ` Tom Tromey
2012-10-24 18:55 ` Jan Kratochvil
2012-10-24 20:18 ` Tom Tromey
2012-10-25 15:54 ` Jan Kratochvil
2012-10-25 16:52 ` Siddhesh Poyarekar
2012-11-06 20:01 ` Jan Kratochvil
2012-11-07 13:48 ` Jan Kratochvil
2012-11-13 19:46 ` Tom Tromey
2012-11-13 19:55 ` Jan Kratochvil
2012-11-01 15:24 ` Jan Kratochvil
2012-11-01 16:56 ` 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=20121003195627.GA17283@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=siddhesh@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