https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100804
--- Comment #2 from George Thopas <george.thopas at gmail dot com> --- After looking at the updated documentation and trying the an update kernel with warning it still leaves some things open. The updated documentation says: "Moreover, the use of type punning or aliasing to toggle the storage order is not supported; that is to say, if a given scalar object can be accessed through distinct types that assign a different storage order to it, then the behaviour is undefined" - In my example the new warning fires on a struct only having chars. I don't see how that is applicable here or how a char array could have a different storage order in either big or little endian. - Regardless of that fact. That field is also never accessed in my example code Al 2 fields of the structs actually read are consistently be (in) and the one written is (out) le. The ones compare are of the same type. Thanks again
