diff options
| author | Uros Bizjak <ubizjak@gmail.com> | 2024-09-09 22:33:52 +0200 |
|---|---|---|
| committer | Uros Bizjak <ubizjak@gmail.com> | 2024-09-09 22:34:29 +0200 |
| commit | 1da79de5275de82bc810d2f8d70fbc98dbce3da5 (patch) | |
| tree | 23ae7da0bfce6222a2372549aa4707227d8c94de /gcc/analyzer/engine.cc | |
| parent | 6e35b0e8572a71d0e6f407cc356592a0b97fc298 (diff) | |
| download | gcc-1da79de5275de82bc810d2f8d70fbc98dbce3da5.zip gcc-1da79de5275de82bc810d2f8d70fbc98dbce3da5.tar.gz gcc-1da79de5275de82bc810d2f8d70fbc98dbce3da5.tar.bz2 | |
i386: Use offsetable address constraint for double-word memory operands
Double-word memory operands are accessed as their high and low part, so the
memory location has to be offsettable. Use "o" constraint instead of "m"
for double-word memory operands.
gcc/ChangeLog:
* config/i386/i386.md (*insvdi_lowpart_1): Use "o" constraint
instead of "m" for double-word mode memory operands.
(*add<dwi>3_doubleword_zext): Ditto.
(*addv<dwi>4_doubleword_1): Use "jO" constraint instead of "jM"
for double-word mode memory operands.
Diffstat (limited to 'gcc/analyzer/engine.cc')
0 files changed, 0 insertions, 0 deletions