Problem solved
Hi I have foujnd the reason for the weird behavior of gcc when reading 64 bits data. I found out how to avoid this. The performance of the generated code doubled. I thank everyone in this forum for their silence to my repeated help requests. They remind me that: THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. Jacob
gcc-13-20231028 is now available
Snapshot gcc-13-20231028 is now available on https://gcc.gnu.org/pub/gcc/snapshots/13-20231028/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 13 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-13 revision a52bc146863af7a12c2212bf7b51e4f276067993 You'll find: gcc-13-20231028.tar.xz Complete GCC SHA256=10ee2194ad4b2bf7c06ddd2dcb89907af58ef4a3ea888f0ad7b9f91103228b02 SHA1=226021dc18781c663ef2f91938c9ff52032a76c0 Diffs from 13-20231021 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-13 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.