https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115096
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- > the warning described in that bug is not occurring. That is because in that case it had literally `(unsigned char**)&var` while in this case it is spread across function calls and that would require a lot of work to get the warning happening. Note there are a few open bug reports specifically asking for a runtime catching of this too; but that is also hard as you need to record the aliasing set of when stores and loads happen.