Instead of outright disabling this completely with the noredzone attribute, we only avoid doing the optimization if there are memory operations between the adjustment and the load/store that the adjustment would be folded into. This avoids the case of something like a stack cookie being corrupted if an exception happens before the pre-increment to the SP occurs.
This also prevents the folding happening if we have a redzone, but the offset being folded is above the redzone amount (128 bytes in this case).
rdar://73269336