Even though ix86_hard_regno_mode_ok doesn't allow xmm16-xmm31 nor
ymm16-ymm31 in 128/256 bit modes when AVX512VL is disabled, reload
can still generate reg to reg moves with xmm16-xmm31 and ymm16-ymm31
in 128/256 bit modes. Remove mode size check in ix86_get_ssemov.
gcc/
PR target/94561
Fixed by r264171.
Tested x86_64-pc-linux-gnu, applying to trunk.
PR c++/86327
* g++.dg/cpp1y/constexpr-return5.C: New test.
---
gcc/testsuite/g++.dg/cpp1y/constexpr-return5.C | 12
1 file changed, 12 insertions(+)
create mode 100644
Hi Folks,
sorry for the long CC list - please feel free to ignore if you don’t care :)
I propose that this PR should be re-categorized as a “C++” one.
The reason is that this is not an oversight in the GCC implementation,
but a problem present in the general case. Library implementors feel
On Tue, 7 Apr 2020, Gustavo Romero via Gcc-patches wrote:
> gcc/Changelog:
> 2020-04-06 Gustavo Romero
>
> * dumpfile.c:
> (selftest::temp_dump_context::temp_dump_context): Fix ctor.
If you approve (David, Jakub, or someone else) I can take care of
committing this if you like.
Hi,
Here is the patch with some of the null pointer tests removed.
This is regression-tested. ChangeLog and test case are as in
https://gcc.gnu.org/pipermail/fortran/2020-April/054193.html .
The list of test cases that fail without the remaining NULL
check is below. Is this OK for trunk?
Best
V4SI, V8HI and V16QI modes of redux__scal_ expander
expand with SSE2 instructions (PSRLDQ and PCMPGTx) so use
TARGET_SSE2 as relevant mode iterator codition.
2020-04-11 Uroš Bizjak
PR target/94494
* config/i386/sse.md (REDUC_SSE_SMINMAX_MODE): Use TARGET_SSE2
condition for V4SI,
