Hi gcc-patches mailing list, Alex Coplan via Sourceware Forge <[email protected]> has requested that the following forgejo pull request be published on the mailing list.
Created on: 2026-07-20 12:58:33+00:00 Latest update: 2026-07-20 12:58:33+00:00 Changes: 2 changed files, 20 additions, 4 deletions Head revision: acoplan/gcc ref fixup-tme-deprecation commit 6d8331082f42748a6675a93515fc4db7f44a211b Base revision: gcc/gcc ref trunk commit a760fee28d361e7f8336c62104d2421a06867424 r17-2555-ga760fee28d361e Merge base: a760fee28d361e7f8336c62104d2421a06867424 Full diff url: https://forge.sourceware.org/gcc/gcc/pulls/195.diff Discussion: https://forge.sourceware.org/gcc/gcc/pulls/195 Requested Reviewers: This is a follow-up patch to Richard E's r17-2498-g17f084306c68c4 (#186 on the Forge). As Alice pointed out in her review: https://gcc.gnu.org/pipermail/gcc-patches/2026-July/724391.html the original patch missed things like +memtag+tme due to the string parsing approach. This instead just inspects the parsed feature flags from aarch64_parse_extension to determine whether to warn in the target attribute/pragma case. +tme on the command line is handled as per Richard's original patch (no change there). gcc/ChangeLog: * config/aarch64/aarch64.cc (aarch64_handle_attr_isa_flags): Warn if +tme is enabled by the target attribute/pragma, relying on the feature flags from aarch64_parse_extension. (aarch64_process_target_attr): Drop +tme warning based on custom string parsing. gcc/testsuite/ChangeLog: * gcc.target/aarch64/deprecate-tme.c: New test. Changed files: - A: gcc/testsuite/gcc.target/aarch64/deprecate-tme.c - M: gcc/config/aarch64/aarch64.cc Alex Coplan (1): aarch64: Fix up TME deprecation warning gcc/config/aarch64/aarch64.cc | 8 ++++---- gcc/testsuite/gcc.target/aarch64/deprecate-tme.c | 16 ++++++++++++++++ 2 files changed, 20 insertions(+), 4 deletions(-) create mode 100644 gcc/testsuite/gcc.target/aarch64/deprecate-tme.c -- 2.54.0
