X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:to:subject:in-reply-to
	:references; q=dns; s=default; b=GxQi7zqU/MHKF18NuSGiJisUnnDesZQ
	TihIrxBICE3PSPNdtjTyhoWkQNbUVt0Rbwy4j54fk76GQpWW0ApOiOB0QB10BH36
	7VXT7p8byohp9w5+/QdnI31E3OkqYqyoV1Bab7FFVujSQzWdoQKZjrdAZ38zIw2a
	lTh0gLtqDT1w=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:to:subject:in-reply-to
	:references; s=default; bh=Xj4YywvAE1JV2dfOLkv97dOFqmw=; b=nR56C
	uHHlNcZBSe87MWvddXqZrk9Jm4521/hVaPEpuuJquq4a2acLarCs3I3n7gwPxQtF
	SY78y9HlQe7KZkVwkXpfjTyBUyNy6vrqL0vDVbjfFLHmNk8Up5oZJcZ/H9cGAYf3
	mNhL0wqZi8E7ZnQpP8HSHRcro5CBHgxktxtOjs=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,SPF_NEUTRAL autolearn=ham version=3.3.1
Message-ID: <20130405113721.3628@binki>
Date: Fri, 05 Apr 2013 11:37:21 +0900
From: wynfield AT gmail DOT com
To: <cygwin AT cygwin DOT com>
Subject: Re: But it is cygwin related.
In-reply-to: Your message of Thu, 04 Apr 2013 22:16:17 -0400         <515E33F1.2060902@cs.umass.edu>
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
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple