[Bug c/101312] ICE with -g and may_alias and qualified (const or volatile) array type

[cvs-commit at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101312

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:9f03e1f3d510e3e42fb85b5269d009f990d1f301

commit r16-7328-g9f03e1f3d510e3e42fb85b5269d009f990d1f301
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Feb 5 14:59:12 2026 +0100

    Revert c, c++: Use c*_build_qualified_type instead of build_qualified_type
from within build_type_attribute

    As seen in PR123882, this broke more than it fixed, a lot of
    build_type_attribute_qual_variant including build_type_attribute_variant
    just pass in TYPE_QUALS (type) as the last argument and for C/C++
    when the code pushes the quals to the element type, it will effectively
    make those unqualified.  The PR123882 ICE is then on the array_as_string
    terrible hack if the FE calls get_aka_type on that, it wants to create
    qualified attribute variant of that and errors on the restrict qual.

    So, to fix both PR c/123882 and other unknown regressions caused by
    PR c/101312 I'm reverting it now.

    This reverts commit 3d2a91a3767982dde5a37abf45c12c08d4fdbf41.