https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115345
--- Comment #6 from Djordje Baljozovic <djordje.baljozovic at ac dot rwth-aachen.de> --- (In reply to Jakub Jelinek from comment #5) > Please see https://gcc.gnu.org/bugs/ for what we need, we need a > self-contained preprocessed testcase, which you haven't provided. > You should start by compiling the code with -fsanitize=undefined and/or > -fsanitize=address, see if it reports anything, if not, create a minimal > self-contained reproducer. Hi, You are pointing me to use fuzzer for our code, which is already done by Google's oss-fuzz project. No issue in the code has been detected in the part of the code I sent. Also, the code itself is not an issue -- it is the GCC executables generated from the very same code that make all the differences, i.e. if the project/code is compiled with GCC 12-14 on one side and GCC 0-11, MSVC (all versions) and Clang (all versions) on the other. Since the code base is rather big, and all functions are intertwined, the only thing I can do is: 1. attach EXE/ELF files and one of the input files which causes the problem 2. create two Docker containers -- one with GCC 11 and one with GCC 12/13/14. 3. I can send you instructions how to compile one part of the project from our GitHub repo. As mentioned in my initial post, gdb crash report is given in the attachment https://gcc.gnu.org/bugzilla/attachment.cgi?id=58344 . Hope this helps. Sincerely, George
