#3 bad behavior on 64-bit platforms

[Bob McElrath]

"long" is used all over the place. I guess the problem
is that on alpha "long int" is 64-bits. This just
about sums it up: (BTW, the "total exection time" comes
out to about 1.7 million years! ;)

(0)<mcelrath@draal:/usr/src/mjpeg_play/lavtools>
fncdump .libs/lav2wav

FunctionChecker V2.0 for gcc (by Y. Perret)
Running profile data file version number 2.0
http://sourceforge.net/projects/fnccheck/

General information:

Profile for '.libs/lav2wav'
Total execution time: 55893634539032.328125 (not main()
time)
Times computed using real clock time.
Number of realloc performed: 0
Unresolved functions not shown : 0
Spontaneous functions not shown : 0
Hidden functions due to -not/-only: 0
Final stack size used: 3
Number of function(s): 4

Flat profile:

| local | total | |
|
| sec. | % | sec. | % | calls |t.
sec/call| name
|-----------|-----|-----------|-----|----------|-----------|--------
|18446744073172.488281| 33.0|18446744073709.363281|
33.0| 1|18446744073709.363281| wav_close
|5032638.783395| 0.0|5032638.783395| 0.0| 9375|
536.814804| do_write
|18446739041637.832031| 33.0| 30.000000| 0.0|
1| 30.000000| main
|18446744069414.585938| 33.0| 0.000001| 0.0|
1| 0.000001| wav_header

Min/MAX time for functions:

indx	MIN	MAX	name
0	18446744073709.363281	18446744073709.363281
wav_close
1	18446744073709.550781	536.874976	do_write
2	30.000000	30.000000	main
3	0.000001	0.000001	wav_header

Call-graph:

'wav_close' [0] called by:
[2],

'do_write' [1] called by:
[3],
[2],
[0],

'main' [2] spontaneously called.

'wav_header' [3] called by:
[2],

[Yannick Perret]

Logged In: YES
user_id=146450

Yes, it was a problem.
But now (V3.0 familly) I only use 'int' or 'long long int'.

I think this trouble will not appear for V3.0 versions.
If you can try it on a 64bit system, please tell me about
your results. If the problem is still present I will correct
it in the 3.0 version (as now I have a more complete
configure, I can handle such cases).

Thank you in advance.