I can answer some questions about assembler...
as conversion from Assembler -> C is what appears to be the case...
When it comes to the OS libcall mechanism thats fine you't have to know the calls and arguments only for the project internal functions...
re-compilation would be interesting but simplistic as long as everything is accounted for
I don't have any style tips for code-layout but suggest you break up the assembler and check what sections are "re-usable" reworking functions accordingly
--- Tony Wyatt wyattaw@optushome.com.au wrote:
Hi Thomas,
On 2/05/2005, you wrote:
Are there any projects up for grabs that I can
look into ?
What about some advice on coding habits? I'd ask privately, but the answer will be of general interest anyway, both in the project I am currently working on and those in the future like OO and Kaffe.
Much old 68k code is fast and efficient because it relies on parameters like library and structure pointers remaining persistent in allocated 68k registers, eg a2, a6 always point to particular structures. In a big module consisting of dozens if not hundreds of very small functions, only one or two registers are ever used for volatile data. Most parameters are passed in assumed registers, so loading of arguments is minimised.
So what is a good way to maintain this register shortcut in a C version of a big program originally written in assembler? Obviously I can specify parameters to be passed in 68k registers, but I am trying to write this thing in a portable fashion, machine-independent.
I have no experience with PPC code yet. Is there a way to ask gcc to use registers for certain parameters, in a platform-independent way? I want the C code to remain pure ANSI-compliant. It would be nice to leave the code unchanged from its present SAS/C environment to PPC and gcc.
cheers
Openoffice-os4 mailing list Openoffice-os4@samfundet.no
https://lists.samfundet.no/mailman/listinfo/openoffice-os4
Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com