[Bug tree-optimization/93210] Sub-optimal code optimization on struct/combound constexpr (gcc vs. clang)

[cvs-commit at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93210

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Stefan Schulze Frielinghaus
<stefansf@gcc.gnu.org>:

https://gcc.gnu.org/g:417c36cfd620bf2b047852c2aa9ac49004aed2bc

commit r11-8186-g417c36cfd620bf2b047852c2aa9ac49004aed2bc
Author: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>
Date:   Thu Apr 15 08:03:47 2021 +0200

    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.