aboutsummaryrefslogtreecommitdiff
path: root/libgomp
diff options
context:
space:
mode:
authorDavid Faust <david.faust@oracle.com>2023-02-14 11:23:01 -0800
committerDavid Faust <david.faust@oracle.com>2023-02-14 14:44:34 -0800
commitc348a717213b03c6661878934f197f4d261f0e56 (patch)
tree5d70417991652e21c9bcea3dd74d10f8a084f31a /libgomp
parenta42ed1d9181d21d5cb02f131f641c0cf375eca9d (diff)
downloadgcc-c348a717213b03c6661878934f197f4d261f0e56.zip
gcc-c348a717213b03c6661878934f197f4d261f0e56.tar.gz
gcc-c348a717213b03c6661878934f197f4d261f0e56.tar.bz2
bpf: fix memory constraint of ldx/stx instructions [PR108790]
In some cases where the target memory address for an ldx or stx instruction could be reduced to a constant, GCC could emit a malformed instruction like: ldxdw %r0,0 Rather than the expected form: ldxdw %rX, [%rY + OFFSET] This is due to the constraint allowing a const_int operand, which the output templates do not handle. Fix it by introducing a new memory constraint for the appropriate operands of these instructions, which is identical to 'm' except that it does not accept const_int. gcc/ PR target/108790 * config/bpf/constraints.md (q): New memory constraint. * config/bpf/bpf.md (zero_extendhidi2): Use it here. (zero_extendqidi2): Likewise. (zero_extendsidi2): Likewise. (*mov<MM:mode>): Likewise. gcc/testsuite/ PR target/108790 * gcc.target/bpf/ldxdw.c: New test.
Diffstat (limited to 'libgomp')
0 files changed, 0 insertions, 0 deletions