diff options
author | Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> | 2021-04-15 08:03:47 +0200 |
---|---|---|
committer | Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> | 2021-04-15 08:04:46 +0200 |
commit | 417c36cfd620bf2b047852c2aa9ac49004aed2bc (patch) | |
tree | b563d68b931c3581ae6dfcec08007cf7e44a6aa5 /gcc/tree-nested.c | |
parent | df3b1289521e6f24d5151fc5f7b135b8bf3009bc (diff) | |
download | gcc-417c36cfd620bf2b047852c2aa9ac49004aed2bc.zip gcc-417c36cfd620bf2b047852c2aa9ac49004aed2bc.tar.gz gcc-417c36cfd620bf2b047852c2aa9ac49004aed2bc.tar.bz2 |
re PR tree-optimization/93210 (Sub-optimal code optimization on struct/combound constexpr (gcc vs. clang))
Regarding test gcc.dg/pr93210.c, on different targets GIMPLE code may
slightly differ which is why the scan-tree-dump-times directive may
fail. For example, for a RETURN_EXPR on x86_64 we have
return 0x11100f0e0d0c0a090807060504030201;
whereas on IBM Z the first operand is a RESULT_DECL like
<retval> = 0x102030405060708090a0c0d0e0f1011;
return <retval>;
gcc/testsuite/ChangeLog:
* gcc.dg/pr93210.c: Adapt regex in order to also support a
RESULT_DECL as an operand for a RETURN_EXPR.
Diffstat (limited to 'gcc/tree-nested.c')
0 files changed, 0 insertions, 0 deletions