https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120051
--- Comment #20 from Iouri Kharon <bc-info at styx dot cabel.net> --- (In reply to Christoph Reiter from comment #19) > After doing some more testing, the 32bit build now fails with these patches: > > [1/301] Compiling C++ object > operations/external/exr-save.dll.p/exr-save.cc.obj > FAILED: operations/external/exr-save.dll.p/exr-save.cc.obj > "ccache" "c++" "-Ioperations/external/exr-save.dll.p" > "-Ioperations/external" "-I../operations/external" "-I." "-I.." "-Igegl" > "-I../gegl" "-Igegl/buffer" "-I../gegl/buffer" "-Igegl/graph" > "-I../gegl/graph" "-Igegl/module" "-I../gegl/module" "-Igegl/opencl" > "-I../gegl/opencl" "-Igegl/operation" "-I../gegl/operation" "-Igegl/process" > "-I../gegl/process" "-Igegl/property-types" "-I../gegl/property-types" > "-IC:/msys64/mingw32/include/babl-0.1" > "-IC:/msys64/mingw32/include/glib-2.0" > "-IC:/msys64/mingw32/lib/glib-2.0/include" > "-IC:/msys64/mingw32/include/gio-win32-2.0" > "-IC:/msys64/mingw32/include/OpenEXR" "-IC:/msys64/mingw32/include/Imath" > "-fdiagnostics-color=always" "-D_GLIBCXX_ASSERTIONS=1" "-Wall" > "-Winvalid-pch" "-std=gnu++14" "-O2" "-g" "-DHAVE_CONFIG_H" > "-DGEGL_ENABLE_DEBUG" "-Winit-self" "-Wmissing-declarations" > "-Wpointer-arith" "-Wno-unused-parameter" "-Wno-cast-function-type" > "-D_FILE_OFFSET_BITS=64" "-gcodeview" "-ftree-vectorize" "-pthread" > "-DLIBDEFLATE_DLL" -MD -MQ > operations/external/exr-save.dll.p/exr-save.cc.obj -MF > "operations/external/exr-save.dll.p/exr-save.cc.obj.d" -o > operations/external/exr-save.dll.p/exr-save.cc.obj "-c" > ../operations/external/exr-save.cc > C:\msys64\tmp\ccR9hXob.s: Assembler messages: > C:\msys64\tmp\ccR9hXob.s:19098: Error: can't resolve .text - Lcvline612 > C:\msys64\tmp\ccR9hXob.s:19100: Error: can't resolve .text - Lcvline612 > C:\msys64\tmp\ccR9hXob.s:19102: Error: can't resolve .text - Lcvline612 > C:\msys64\tmp\ccR9hXob.s:19104: Error: can't resolve .text - Lcvline612 > C:\msys64\tmp\ccR9hXob.s:19106: Error: can't resolve .text - Lcvline612 > C:\msys64\tmp\ccR9hXob.s:19108: Error: can't resolve .text - Lcvline612 > C:\msys64\tmp\ccR9hXob.s:19110: Error: can't resolve .text - Lcvline612 > C:\msys64\tmp\ccR9hXob.s:19112: Error: can't resolve .text - Lcvline612 > C:\msys64\tmp\ccR9hXob.s:19114: Error: can't resolve .text - Lcvline612 > ... Try removing the -g switch from the command line (leaving -gcodeview) - the combination of the -gcodeview -g switches (and in that order!) leads to such errors. Well, only those who know what SHOULD happen with such a combination of switches can "fix" it :). And it seems to me that it is worth opening a separate ticket about this situation (it appears on any source) and is not directly related to codeview generation errors.
