This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hi. I'm forwarding the following message to the list for a collegue who needs some documentation on some low-level crossgcc issues. He's currently using an m68k MRI cross-compiler on a sparc, but I recently built him an m68k-coff crossgcc toolset under cygwin on NT. He likes it, but he has some issues that need resolving before we can put it to use. Any pointers to docs would be greatly appreciated. TIA. > I'm having difficulty finding documentation on the following: > > The C calling conventions (i.e., exactly how parameters are pushed onto the > stack so we can call C subroutines from assembly language, and vice versa). > How a C subroutine returns a value to the assembly routine that called it > (e.g., MRI returns values from C subroutines in register D0). > What registers, if any, a C subroutine will preserve and destroy (our legacy > code makes major assumptions based on registers that MRI preserves for the > assembly code). > > If you'd like to see the type of information that MRI provides, see chapter 6 of > the MRI C Compiler Reference Manual. -- fred anger - anger@triib.com http://www.triib.com/anger/ ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |