Feature request: codiff only considering file basename

Feature request: codiff only considering file basename

[Diego 'Flameeyes' Pettenò]

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]


I found myself today in the situation of using codiff on two binaries
built with the same sources, but reorganised around; since I noticed a
non-zero difference on codiff, I would have liked to know where the
difference would be, but since the source files' path has changed,
codiff is showing me too much noise and I can't figure out what changed.

Optionally considering the basename of the source files would be very
nice way to reduce the noise and only show the important data.

Thanks!

P.S.: is a new release to be expected? Or git is going to be the only
way?

-- 
Diego "Flameeyes" Pettenò
http://blog.flameeyes.eu/


[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]

Re: Feature request: codiff only considering file basename

[Arnaldo Carvalho de Melo]

Em Fri, Oct 24, 2008 at 03:12:58PM +0200, Diego 'Flameeyes' Pettenò escreveu:
> 
> I found myself today in the situation of using codiff on two binaries
> built with the same sources, but reorganised around; since I noticed a
> non-zero difference on codiff, I would have liked to know where the
> difference would be, but since the source files' path has changed,
> codiff is showing me too much noise and I can't figure out what changed.
> 
> Optionally considering the basename of the source files would be very
> nice way to reduce the noise and only show the important data.

Can you show an excerpt of the output you would like to see changed?
 
> Thanks!
> 
> P.S.: is a new release to be expected? Or git is going to be the only
> way?

I was expecting to make a release with the CTF encoder, but will try and
get one out RSN with what is in git.

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe dwarves" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Feature request: codiff only considering file basename

[Diego 'Flameeyes' Pettenò]

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

Arnaldo Carvalho de Melo <acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
writes:

> Can you show an excerpt of the output you would like to see changed?

Sorry for the delay, very long days lately :(

flame@yamato mytmpfs % echo "int foo() { return 1; }" > foo.c
flame@yamato mytmpfs % gcc -ggdb -c foo.c 
flame@yamato mytmpfs % gcc -ggdb -c ./foo.c -o foo2.o
flame@yamato mytmpfs % codiff foo.o foo2.o
foo.c:
  foo |  -11
 1 function changed, 11 bytes removed, diff: -11

./foo.c:
  foo |  +11
 1 function changed, 11 bytes added, diff: +11

foo2.o:
 2 functions changed, 11 bytes added, 11 bytes removed, diff: +0

This is what I mean as a problem, as a solution I'd check for just the
basename (so that foo.c and ./foo.c become the same file) or, much more
complicated but would really be nice, I'd check if all the symbols gone
From one file appeared on another, so that the output would then become:

flame@yamato mytmpfs % codiff foo.o foo2.o
 File renamed: was foo.c is ./foo.c

But that's going to be hard :P

-- 
Diego "Flameeyes" Pettenò
http://blog.flameeyes.eu/

[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]