At 01:44 PM 5/6/2002 -0400, you wrote: >When I try to build parrot with gcc, I get 754 warnings. Obviously I >won't post them all here, but some typical ones are:
Firstly I just did a big patch to make the bytecode portable, so thats the reason you are seeing packfile issues, however they aren't all from myself... *halo* >packfile.c:48: warning: passing arg 1 of `mem_sys_allocate' with different >width due to prototype I saw this too in the original code. I don't understand why we use UINTVAL everywhere, sometimes I follow what was there before. It appears, for example, with mem_sys_allocate() that it once took an UINTVAL and was changed to size_t but many of the calls didnt change. Definitely, all these casts of sizeof() are not correct. >Not unexpectedly, 'make test' is a total failure, with lots of >lines of the form: > >t/op/basic..........# Failed test (t/op/basic.t at line 6) ># got: 'PackFile_unpack: Not a Parrot PackFile! ># Parrot VM: Can't unpack packfile t/op/basic1.pbc. ># ' ># expected: '' > >I'm not sure where to even start. There are a variety of places where >casts to (INTVAL) or (UINTVAL) are used even though the receiving end >is actually expecting something else (e.g. size_t). > >If anyone is looking into this, please speak up. I haven't been >following the group closely for a while. If no one else is, then I'll >take a look, but I can't promise a rapid response. I'm working on some of them. I saw quite a few issues while reworking the bytecode format for cross-platform. I'll commit a few cleanups shortly. -Melvin
