https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101377
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-07-08
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> So it's likely the issue that mingw/cygwin do not like executables with
> DWARF5 debug and g:cfc9fdcec8861be0d11ec4493cca518bf5b4c32d somehow
> autodetects support for it in gas which then, despite GCC defaulting to DWARF4
> ends up emitting DWARF5 by means of --gdwarf-5 passed to it?
Binutils 2.36 should be detected as HAVE_LD_BROKEN_PE_DWARF5 by the configure
script and DWARF 4 forced by:
#ifdef HAVE_LD_BROKEN_PE_DWARF5
/* If the PE linker has broken DWARF 5 support, make
DWARF 4 the default. */
if (TARGET_PECOFF)
SET_OPTION_IF_UNSET (opts, opts_set, dwarf_version, 4);
#endif
so --gdwarf-5 should not be passed, but something obviously does not work.
Could you post the *couple* of lines from config.log starting with:
configure:30285: checking broken PE linker dwarf5 support
