https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90676
Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org --- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> --- Dropping the access type is like printing 'memset(a, 0)' and dropping the size argument. I think the simplest solution for MEM_REF is to mention the type. It may not include all the detail we might be interested in but it does provide the most essential information. Patch: https://gcc.gnu.org/ml/gcc-patches/2019-06/msg00011.html (PR 87052 and PR 90694 are a couple other examples that we've fixed in the past to get more meaningful/reliable dumps.)