This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Function call difference between cygwin and Windows


If a function calls both cygwin and Windows functions the binary creates
extra subroutine (in assembly) for cygwin ones. Example:

* Windows function:

   call cs:CreatePipe

* cygwin function:

   call ioctl

   ioctl proc near
   jmp cs:__imp_ioctl
   endp

The binary is statically compiled. Why there are extra subroutines? Is this
"by-design"? Or am I missing something?

--
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]