https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93731
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to r...@cebitec.uni-bielefeld.de from comment #7) > > --- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot > > Uni-Bielefeld.DE> --- > >> --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > [... > >> Of course, trying to workaround kernel bugs this way is weird, but if it > >> isn't > >> supported anymore or Apple isn't willing to fix their bugs... > > > > Mac OS X 10.7 is almost 9 years old by now and long past support. I > > don't feel particularly inclined to reghunt which gcc/sanitizer change > > caused this, let alone debug the Darwin kernel either. > > I've since experimented a bit more: 32-bit 10.7 is affected just the > same. Afterwards, I've copied both the 32 and 64-bit > alloca_big_alignment.exe and the corresponding libasan.6.dylib and > libgcc_s.1.dylib to a 10.8 VM where they run just fine, so this is > obviously 10.7-only issue. Yeah, I'm just waiting for the x86_64-darwin13 run to finish with libsanitizer disabled (the fault repeats for me on 64b). It's early low on my priority list to look at this with the current sanitiser output, since that is emitting a different ABI for Darwin than clang does (so the emitted code would be the first thing to fix). > While working on this, I've created VirtualBox VMs for every single > macOS release between 10.7 and 10.15, each with the latest updates and > last supported Xcode version installed and ready for experiments if > needed. VB is more reliable for some versions than others (which might have little to do with VB, of course ;) ). It's pretty hard to get anything < 10.6 to work there, and obv. is no use of ppc. ---- Right now, I'm thinking to disable sanitzer by default for master <= 10.7 and for 9.x for <= 10.6. I'll do that today or tomorrow since I want to make the 9.3 deadline.
