Am 4. Juni 2026 15:47:00 MESZ schrieb oscar pablo di liscia <[email protected]>: > >I’ve used mingw64 for the latest version of Pure Data Vanilla. [...] >but with severe memory >issues when i run them in PD.
a few observations: - virtually all externals for macOS built in the last decade (or two), are built with clang (I don't remember when Apple ditched GCC in favour of clang, but probably around the time when they switched to 64bit Intel) - if your external has memory issues, it's most likely a fault with the external. compilers (and operating systems) have some liberties on how to allocate/arrange memory, which can result in hiding memory issues in your code (that is: a memory issue might show itself when you switch compilers). but the issue is still in the code, rather than the compiler. to debug memory issues, use a debugger, eg valgrind. -in Windows things are a bit more complicated, as different MinGW environments use different libc implementations and they might not be fully interchangeable. the arm64 binaries for Pd are built using the "mingw-w64-x86_64" environment (which uses the old msvcrt libc implementation; *and* uses GCC s the compiler). other environments (mingw-w64-ucrt-x86_64, but I believe mingw-w64-clang64-x86_64 too!) use different libc implementations (the new ucrt), and that might give you weird results, esp. when using resources allocated by one libc with functions from another. I'm pretty sure I had problems using zexy's [regexp] object when compiling zexy with ucrt in a normal mingw64 Pd. so to summarize: - fix the memory issues in your externals:-) - on windows, use the same msys environment that was used to build Pd (mingw64) mfg.sfg.jfd IOhannes --- [email protected] - the Pure Data mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/BBY5WVZQRSJIHZZPAF5JZNZYRP2ZV2U4/ To unsubscribe send an email to [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
