Hi gcc-patches mailing list, Richard Earnshaw <[email protected]> has requested that the following forgejo pull request be published on the mailing list.
Created on: 2025-11-10 14:51:54+00:00 Latest update: 2025-11-10 14:52:36+00:00 Changes: 1 changed files, 3 additions, 3 deletions Head revision: rearnsha/gcc-TEST ref hf-vsel-bug2 commit dbc9d1dade3fa53be7bbef3b90691ab6a84323a3 Base revision: gcc/gcc-TEST ref trunk commit a98b6cf01ba9fb69450a5e883c5d8e8600e2cc95 r16-5118-ga98b6cf01ba9fb Merge base: a98b6cf01ba9fb69450a5e883c5d8e8600e2cc95 Full diff url: https://forge.sourceware.org/gcc/gcc-TEST/pulls/122.diff Discussion: https://forge.sourceware.org/gcc/gcc-TEST/pulls/122 Requested Reviewers: The define_expand patterns for movdfcc, movsfcc and movhfcc had overly tight contstraints that could cause the compiler to reject these patterns when re-ordering the operands could lead to a successful match. Relax the initial predicate test and rely on the test after arm_validize_comparison has run to determine whether this is something we can support. This fixes some test failures which were introduced in the fix for PR118460 gcc/ChangeLog: PR target/118460 * config/arm/arm.md (movhfcc): Use expandable_comparison_operator. (movsfcc, movdfcc): Likewise. Thanks for taking the time to contribute to GCC! Please be advised that https://forge.sourceware.org/ is currently a trial that is being used by the GCC community to experiment with a new workflow based on pull requests. Pull requests sent here may be forgotten or ignored. Patches that you want to propose for inclusion in GCC should use the existing email-based workflow, see https://gcc.gnu.org/contribute.html Changed files: - M: gcc/config/arm/arm.md Richard Earnshaw (1): arm: Don't reject early mov?fcc patterns that we might be able to handle gcc/config/arm/arm.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- 2.51.1
