aboutsummaryrefslogtreecommitdiff
path: root/gcc/fortran/resolve.c
diff options
context:
space:
mode:
authorRoger Sayle <roger@nextmovesoftware.com>2021-10-15 19:09:25 +0100
committerRoger Sayle <roger@nextmovesoftware.com>2021-10-15 19:09:25 +0100
commit730f52e05a1fb5c8cd92e352e9b191a6332be5c2 (patch)
tree02681e0721aae3013e14b323f38bbafaf26e4ceb /gcc/fortran/resolve.c
parent2c564e813c0626802e5bfb066c094933d5e6a774 (diff)
downloadgcc-730f52e05a1fb5c8cd92e352e9b191a6332be5c2.zip
gcc-730f52e05a1fb5c8cd92e352e9b191a6332be5c2.tar.gz
gcc-730f52e05a1fb5c8cd92e352e9b191a6332be5c2.tar.bz2
Allow early sets of SSE hard registers from standard_sse_constant_p.
My previous patch, which was intended to reduce the differences seen by the combination of -march=cascadelake and -m32, has additionally found some more instances where this combination behaves differently to regular x86_64-pc-linux-gnu. The middle-end always, and backends usually, use emit_move_insn to emit/expand move instructions allowing the backend control over placing things in constant pools, adding REG_EQUAL notes, and so on. Several of the AVX512 built-in expanders bypass this logic, and instead generate moves directly using emit_insn(gen_rtx_SET (dst,src)). For example, i386-expand.c line 12004 contains: for (i = 0; i < 8; i++) emit_insn (gen_rtx_SET (xmm_regs[i], const0_rtx)); I suspect that in this case, loading of standard_sse_constant_p, my change to require loading of likely spilled hard registers via a pseudo is perhaps overly strict, so this patch/fix reallows these immediate constants values to be loaded directly prior to reload. 2021-10-15 Roger Sayle <roger@nextmovesoftware.com> gcc/ChangeLog * config/i386/i386.c (ix86_hardreg_mov_ok): For vector modes, allow standard_sse_constant_p immediate constants.
Diffstat (limited to 'gcc/fortran/resolve.c')
0 files changed, 0 insertions, 0 deletions