This is the mail archive of the
mailing list for the Cygwin project.
Re: But it is cygwin related.
- From: wynfield at gmail dot com
- To: <cygwin at cygwin dot com>
- Date: Fri, 05 Apr 2013 11:37:21 +0900
- Subject: Re: But it is cygwin related.
- References: <20130404170527 dot 3708 at binki> <20130404085538 dot GE25170 at calimero dot vinschen dot de> <515D78B1 dot 60209 at farance dot com> <CA+sc5mmQ9rJ85rvDbMTvp_+vCx6CQPava5N3-8yxd9soh6zxQg at mail dot gmail dot com> <20130404230429 dot 3100 at binki> <20130404144050 dot GA779 at ednor dot casa dot cgf dot cx> <20130405094541 dot 1104 at binki> <515E33F1 dot 2060902 at cs dot umass dot edu>
Another great idea. I'll give it go. Thank you.
Eliot Moss wrote:
> It sounds as if what you need to know is the calling
> convention for gcc on the x86. Maybe the easiest
> thing is simply to write and compile some C programs
> and then use gdb to disassemble them (or request
> assembly code output from gcc). Since you presumably
> grok x86 assembly, this should not be too hard. The
> C programs in question can include calls to all the
> routines you want to call from assembly.
> Then you write your .s file, assemble it to .o, and
> link as usual. It might take some linker flag fiddling
> to get exactly what you want, but I don't think this
> is all that deep.
> Regards -- Eliot Moss
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple