I'm reading a white paper published by Sun regarding the porting efforts
from SPARC to x86. I summarized as below but has questions inlined.
Easy part
(1) If the application is in Java language, then it's non-port.
(2) For driver code, if it uses standard DDI/DDK kernel interface, it's just
div id=jive-html-wrapper-div
div id=mb_0
divI'm reading a white paper published by Sun
regarding the porting efforts from SPARC to x86.
Where is the white paper? I would be interested in passing it to Mathworks to
try to encourage them to port MATLAB from SPARC to x86.
This message
jeff Gray writes:
(2) For driver code, if it uses standard DDI/DDK kernel interface, it's just
recompile, no need to change. Defore Sun open source the code 2+ years ago,
is it likely to develop such driver using non-standard kernel interface for
a driver?
Yes, such non-Sun-developed code
You can just google Porting Guidelines For Solaris Operating System, x86
Platform Edition I also see lots of tools from Sun helping the migration,
but haven't had any experience on them.
On 12/13/07, Dr. David Kirkby [EMAIL PROTECTED] wrote:
div id=jive-html-wrapper-div
div id=mb_0
divI'm
Dr David Kirby said:
I'm reading a white paper published by Sun regarding the porting efforts from
SPARC to x86. Where is the white paper? I would be interested in passing it to
Mathworks to try to encourage them to port MATLAB from SPARC to x86.
The Mathworks products I've researched are
[...]
(4) Platform dependent code
like #ifdef SPARC code. What are the
typical example of platform (SPARC vs.
x86) dependent code?
Plenty. #ifdef SPARC is inappropriate as a way to identify Solaris, use it
only if you really
are doing something essentially SPARC-specific. Many people think
