Originally Posted by romracer
2) This replicates the setup already in place by Android itself on your /system partition. The libraries in /su/lib (or /system/lib in a non-systemless Xposed) are used by the 32-bit Zygote (and some of the *oat tools in /system/bin). The same is true of the libraries in /su/lib64 or /system/lib64; they are used by the 64-bit Zygote. Android has no /system/lib32 (at least my Nexus phones don't). Are you proposing the layout set forth by Android should be abandon when placing files into /su's file system?
/su was created for SuperSU, what the layout is in /system is irrelevant, it was never meant to reflect /system. SuperSU installs the most-bits version of its tools (32-bits on 32-bit devices, 64-bit on 64-bit devices) in /su/bin and /su/lib. It has never made the distinction because there's always only one version installed.
I am not proposing anything. I am simply warning that this can potentially end up mixing 32-bit and 64-bit libraries in the same folder, which is a jolly bad idea, and it will at some point end up making some binary malfunction. A work-around is using lib32 and lib64 instead (or if the entire folder is going to be bound, lib32_bind and lib64_bind).