* Re: diff vs codiff against empty
[not found] ` <Pine.LNX.4.64.0801302133380.5832-Y/UOj9v5BLQhZigby9b+C6cUovnZ0M2TMR2xtNvyitY@public.gmane.org>
@ 2008-01-31 12:08 ` Arnaldo Carvalho de Melo
0 siblings, 0 replies; only message in thread
From: Arnaldo Carvalho de Melo @ 2008-01-31 12:08 UTC (permalink / raw)
To: Ilpo Järvinen; +Cc: dwarves-u79uwXL29TY76Z2rM5mHXA
Em Wed, Jan 30, 2008 at 09:42:18PM +0200, Ilpo Järvinen escreveu:
> Hi,
>
> Not a bad problem but makes some tricks I do harder than they would need
> to be:
>
> ijjarvin@kivilampi-30:~/work/src/submit$ diff /dev/null lib/jhash.o
> Binary files /dev/null and lib/jhash.o differ
> ijjarvin@kivilampi-30:~/work/src/submit$ codiff /dev/null lib/jhash.o
> codiff: /dev/null: not a valid ELF file
[acme@doppio examples]$ codiff /dev/null hello
hello.c:
main | +47
1 function changed, 47 bytes added, diff: +47
[acme@doppio examples]$ codiff hello /dev/null
hello.c:
main | -47
1 function changed, 47 bytes removed, diff: -47
[acme@doppio examples]$
> I.e., I created new file jhash and just want to diff it against empty. I
> also tried codiff against echo "" | gcc -g -c -o lib/jhash.o.base -x c -
> but that wasn't any better. I can fix that with sed trick by using pfunct
> -s for it first though.
>
> Btw, codiffs help/usage printout is incorrect or uses unusual notation, it
> uses [] brackets around old_file and new_file even though they are not
> optional arguments.
Fixed in all the dwarves, thanks.
- Arnaldo
^ permalink raw reply [flat|nested] only message in thread