Ewrin wrote:
>Both the "old" 16-bit PIC binaries as well as my 32-bit patch use
>the same flat format, and both can be converted with coff2flt.
>You can even mix 16-bit and 32-bit PIC objects as long as
>a) the 16-bit objects have no references to modules that are >32K away,
>and
>b) you don't call functions inside 16-bit object modules from 32-bit
modules.
>
After some thought, I realized that mixing 16bit-pic object and 32bit-pic
object
is not a good idea. because
a) the 16-bit objects have no references to modules that are >32K away
---------> Checking some functions in 32bit object still remains <32K
range
after some source changes, would be a tedious job.
Therefore a) means "16bit object cannot call 32bit
functions in general"
b) you don't call functions inside 16-bit object modules from 32-bit modules
----------> We couldn't live without standard library.
Therfore b) means "32bit object cannot call 16bit
functions in general"
Therefore a),b) means mixing 16/32-pic object is not practical.
Then we have a choice between 16bit-pic app(16b obj+16bit lib) and
32bit-pic app.(32b obj+32b lib)
and trade off must be a speed/codesize.
Jeff, could i see m68k-pic32-coff-* tools in the next uClinux tool chains
(If 32bit-pic approved "clean" by everyone) ?
This message resent by the ucsimm@uclinux.com list server http://www.uClinux.com/
This archive was generated by hypermail 2b30 : Sun Apr 07 2002 - 00:01:33 EST