https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99581
--- Comment #9 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #8) > Rather than a target hook, isn't it a property of a particular constraint? > This constraint implies "m", this one doesn't? > Make the implies "m" behavior the default one and add some syntax in the > *.md files to declare constraints that have the new behavior? > Kind like define_memory_constraint vs. define_special_memory_constraint > difference. Yes, I think it is better solution. I guess aarch64 might have the same problem as in this PR. We should have different treatment of memory constraints even for one target.
