https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100530
--- Comment #18 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rgue...@gcc.gnu.org>: https://gcc.gnu.org/g:319f1d042179b381becf4bf1d0f6b9dab6e84884 commit r15-7301-g319f1d042179b381becf4bf1d0f6b9dab6e84884 Author: Richard Biener <rguent...@suse.de> Date: Fri Jan 31 08:56:39 2025 +0100 debug/100530 - Revert QUAL_ADDR_SPACE handling from dwarf2out.cc The bug clearly shows that r8-4385-ga297ccb52e0c89 was wrong in enabling handling of address-space qualification as DWARF type qualifiers as the code isn't prepared to it actually be not handled and ends up changing a lesser qualified (without address-space) type DIE in ways tripping asserts. The following reverts that part which then causes the DIE for the same type with address-space qualifiers removed to be re-used since there's currently no code to encode address-spaces within dwarf2out.cc or in the DWARF spec. r8-4385-ga297ccb52e0c89 did not come with a testcase nor a good description of the bug fixed - I've verified const qualification mixed with address-spaces creates the expected DWARF. PR debug/100530 * dwarf2out.cc (modified_type_die): Do not claim we handle address-space qualification with dwarf_qual_info[]. * gcc.target/i386/pr100530.c: New testcase.