On Thu, 14 Dec 2006, Bob wrote:
The problems frankly look pretty trivial. As in my original posting, casting pointers to integers being the most likely culprit for causing runtime failures given the size difference between a 64 bit pointer and a 32 bit integer.
I doubt very much that those warnings of pointer/int casts point to the problem. As long as the compiler does the normal longtype -> shorttype cast action of lopping off high order bits, all is well (and it would be silly for the compiler to do anything else).
The problem is probably something far more insidious, having to do with different-sized object pointers and alignment. Prototyping doesn't catch this, and the compiler is thus silent on the problem. I've fixed one of these already, but there are undoubtably many more.
The only way is to slog through the swamp, feel around for alligators one by one, and pull them out of their holes by the tail without getting chomped.
Put another way, I'd probably have to move all my mail to the target system and run that way for some time until all the swamp critters have come out of hiding and have been skinned.
As for providing access to a 64 bit development system - Solaris 10 with gcc 4.1.1, I would be happy too - and no I don't expect it to take a few minutes and I would be willing to pay for your time if that helps.
I appreciate the offer, but this is probably not something that can be done by ssh'ing in to a remote system.
-- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
