aboutsummaryrefslogtreecommitdiff
path: root/gcc/cp
diff options
context:
space:
mode:
authorAndrew Pinski <quic_apinski@quicinc.com>2024-04-10 13:39:01 -0700
committerAndrew Pinski <quic_apinski@quicinc.com>2024-04-12 10:34:24 -0700
commit245595d72818526e2ca857848831e8afa87ae2de (patch)
tree843162598260b392bc099e624641d1dbbfce1fbd /gcc/cp
parent9b8c6fffcb199b51bb9c4f46f2834f5fd0149d01 (diff)
downloadgcc-245595d72818526e2ca857848831e8afa87ae2de.zip
gcc-245595d72818526e2ca857848831e8afa87ae2de.tar.gz
gcc-245595d72818526e2ca857848831e8afa87ae2de.tar.bz2
match: Fix `!a?b:c` and `a?~t:t` patterns for signed 1 bit types [PR114666]
The problem is `!a?b:c` pattern will create a COND_EXPR with an 1bit signed integer which breaks patterns like `a?~t:t`. This rejects when we have a signed operand for both patterns. Note for GCC 15, I am going to look at the canonicalization of `a?~t:t` where t was a constant since I think keeping it a COND_EXPR might be more canonical and is what VPR produces from the same IR; if anything expand should handle which one is better. Bootstrapped and tested on x86_64-linux-gnu with no regressions. PR tree-optimization/114666 gcc/ChangeLog: * match.pd (`!a?b:c`): Reject signed types for the condition. (`a?~t:t`): Likewise. gcc/testsuite/ChangeLog: * gcc.c-torture/execute/bitfld-signed1-1.c: New test. Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
Diffstat (limited to 'gcc/cp')
0 files changed, 0 insertions, 0 deletions