That issue only relates to data corruption in the case of major failures like power loss and kernel panics. In most of those situations some data loss is not only expected but also the least of your concerns.
As for the original topic, the first thing to check is the usual problems moving between architectures like endianess, definition of data structures (is long really 32 bits, double 64 bits, etc), memory alignment and compiler settings. Does the code work with all of the optimizations turned off? On Fri, Aug 12, 2022 at 5:58 AM Bastiaan van den Berg <b...@spacedout.nl> wrote: > Did you read that M1's storage has so much cache + lies to the OS about > cache commitments, leading to data corruption sometimes? > https://twitter.com/marcan42/status/1494213855387734019 > > On Fri, Aug 12, 2022 at 6:14 AM Jaime Oliver <jaime.oliv...@gmail.com> > wrote: > >> Dear all, >> >> I have a c external that compiles and runs fine on windows, Linux, and >> Mac Intel systems, but while the exact same code compiles ok on a Mac M1 >> system, it runs with errors. >> >> I am trying to figure out the bug, but wonder if anyone has come across >> something like this? The external itself is not particularly complex. It >> writes and reads text files, does basic arithmetic, and uses arrays of >> various sizes. >> >> Does anyone have any suggestions of where to look first? >> >> Best, >> >> Jaime >> _______________________________________________ >> Pd-list@lists.iem.at mailing list >> UNSUBSCRIBE and account-management -> >> https://lists.puredata.info/listinfo/pd-list >> > _______________________________________________ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list >
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
