On 2023-12-17 22:22, Dan Shelton via Cygwin wrote: > It would be nice if someone from the Cygwin authors could assist me in > figuring out why this happens.
Cygwin is famously slow; this is nothing new. We are grateful for Cygwin because it makes stuff work at all; if it were blazing fast that would be a bonus. E.g. git operations (clone, rebase, ...); ./configure scripts; ...: all run like molasses. The following is just my fast and loose opinion, shot from the hip, and possibly off or wrong, but it likely has to do with the layering. Cygwin's core API is based on a C library called Newlib. Cygwin bolts Newlib to Windows by means of an additional shim below Newlib that is based on C++ objects, where there is path munging going on and such, and that's where the Win32 calls get made. It's an additional abstraction. I worked with the internals a bit when producing the Cygnal project. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
