aboutsummaryrefslogtreecommitdiff
path: root/gcc/value-range.h
diff options
context:
space:
mode:
authorKewen.Lin <linkw@gcc.gnu.org>2022-08-16 00:24:07 -0500
committerKewen Lin <linkw@linux.ibm.com>2022-08-16 00:24:07 -0500
commit9367e3a65f874dffc8f8a3b6760e77fd9ed67117 (patch)
tree345d19f64aa9ef58719fb6f23abea26654e9a2ce /gcc/value-range.h
parent5239e2bd48fb1e6a1d1b06a1bac49bee0a742e98 (diff)
downloadgcc-9367e3a65f874dffc8f8a3b6760e77fd9ed67117.zip
gcc-9367e3a65f874dffc8f8a3b6760e77fd9ed67117.tar.gz
gcc-9367e3a65f874dffc8f8a3b6760e77fd9ed67117.tar.bz2
rs6000: Adjust mov optabs for opaque modes [PR103353]
As PR103353 shows, we may want to continue to expand built-in function __builtin_vsx_lxvp, even if we have already emitted error messages about some missing required conditions. As shown in that PR, without one explicit mov optab on OOmode provided, it would call emit_move_insn recursively. So this patch is to allow the mov pattern to be generated during expanding phase if compiler has already seen errors. PR target/103353 gcc/ChangeLog: * config/rs6000/mma.md (define_expand movoo): Move TARGET_MMA condition check to preparation statements and add handlings for !TARGET_MMA. (define_expand movxo): Likewise. gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr103353.c: New test.
Diffstat (limited to 'gcc/value-range.h')
0 files changed, 0 insertions, 0 deletions