Re: But it is cygwin related.

2013-04-04 Thread wynfield
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 o

Re: But it is cygwin related.

2013-04-04 Thread d.henman
Comments below: Christopher Faylor wrote: > If you're asking how to call cygwin entry points to use Cygwin I/O from > an assembly language program then you are on-topic for the mailing list. That's exactly what I asked. > It is possible to write a raw assembly language program which does this >

Re: But it is cygwin related.

2013-04-04 Thread Eliot Moss
On 4/4/2013 5:05 PM, Christopher Faylor wrote: On Thu, Apr 04, 2013 at 02:59:01PM -0400, Eliot Moss wrote: If you have to enter MinGW land to perform what the OP wants then that is a really clear indication that this is off-topic. Agreed ... we have now directed him to at least two useful pl

Re: But it is cygwin related.

2013-04-04 Thread Christopher Faylor
On Thu, Apr 04, 2013 at 02:59:01PM -0400, Eliot Moss wrote: >On 4/4/2013 2:40 PM, Eliot Moss wrote: >>It occurred to me to mention to the OP that the mingw package (minimal >>Gnu for Windows is what I think it stands for) is a lighter weight >>version of the gcc stuff for Windows. It does not try

Re: But it is cygwin related.

2013-04-04 Thread Eliot Moss
On 4/4/2013 2:40 PM, Eliot Moss wrote: It occurred to me to mention to the OP that the mingw package (minimal Gnu for Windows is what I think it stands for) is a lighter weight version of the gcc stuff for Windows. It does not try to "fake" a Linux environment to the extent that cygwin does, so

Re: But it is cygwin related.

2013-04-04 Thread Eliot Moss
It occurred to me to mention to the OP that the mingw package (minimal Gnu for Windows is what I think it stands for) is a lighter weight version of the gcc stuff for Windows. It does not try to "fake" a Linux environment to the extent that cygwin does, so it is simpler and smaller, as I understa

Re: But it is cygwin related.

2013-04-04 Thread Enrique Perez-Terron
On Thu, 04 Apr 2013 17:46:12 +0200, Frank Farance wrote: [snip] Now, for whatever reason, a different set of calculations are needed and assembler is the best software engineering solution (for whatever reason). As a programmer, I can think of several ways that will cause a visual image

Re: But it is cygwin related.

2013-04-04 Thread Frank Farance
On 2013-04-04 09:15, Earnie Boyd wrote: On Thu, Apr 4, 2013 at 8:57 AM, Frank Farance wrote: I haven't posted in a long while, but the question seems reasonable and relevant to cygwin. If one were writing assembler code to be compatible with cygwin, one would need the answer to the question or

Re: But it is cygwin related.

2013-04-04 Thread Eliot Moss
A C program is going to want to pull in at least a C run-time (crt0 is one common name for that link file). Consider this minimal C program: extern void exit(int); void main (int argc, char **argv) { exit(0); } It is 73 bytes as a .c file and 408 bytes in a .o. It I link it, doing what gcc d

Re: But it is cygwin related.

2013-04-04 Thread Christopher Faylor
On Thu, Apr 04, 2013 at 11:04:29PM +0900, wynfield wrote: >No Earnie. It wasn't about programming. Read and try to comprehend. >cygwin seems to have a missing api in it or one it should have is >missing. The cygwin.dll or possibly another cygwin dll shuffles i/o >betwwen cygwin programs and MSWi

Re: But it is cygwin related.

2013-04-04 Thread wynfield
No Earnie. It wasn't about programming. Read and try to comprehend. cygwin seems to have a missing api in it or one it should have is missing. The cygwin.dll or possibly another cygwin dll shuffles i/o betwwen cygwin programs and MSWindows is not open to linkage (or is it) by assembly language

Re: But it is cygwin related.

2013-04-04 Thread Earnie Boyd
On Thu, Apr 4, 2013 at 8:57 AM, Frank Farance wrote: > > I haven't posted in a long while, but the question seems reasonable and > relevant to cygwin. If one were writing assembler code to be compatible > with cygwin, one would need the answer to the question originally posed. I > don't see this

Re: But it is cygwin related.

2013-04-04 Thread Frank Farance
On 2013-04-04 04:55, Corinna Vinschen wrote: On Apr 4 17:05, wynfi...@gmail.com wrote: It is a cygwin related question to me. It involves using cygwin and programs built using cygwin. You are wrong to suggest that it doesn't related to cygwin. Additionally it involves using cygwin as a lear

Re: But it is cygwin related.

2013-04-04 Thread Corinna Vinschen
On Apr 4 17:05, wynfi...@gmail.com wrote: > > It is a cygwin related question to me. It involves using cygwin and > programs built using cygwin. You are wrong to suggest that it doesn't > related to cygwin. Additionally it involves using cygwin as a > learning and buiding tool. You should con

But it is cygwin related.

2013-04-04 Thread wynfield
It is a cygwin related question to me. It involves using cygwin and programs built using cygwin. You are wrong to suggest that it doesn't related to cygwin. Additionally it involves using cygwin as a learning and buiding tool. You should consider a more constructive response that would be h