[Bug c++/84322] -fstrong-eval-order violated on assignment with function call

[redi at gcc dot gnu.org]

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2018-02-14
     Ever confirmed|0                           |1

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Confirmed.

(In reply to Oleg Oshmyan from comment #0)
> Here are my gcc -v and uname -a, which I doubt will be useful but are
> requested on https://gcc.gnu.org/bugs/:

Thank you for providing them though.

> For reference, I have also tried GCC 6.3.0 and 5.1.0 (which do not
> understand -fstrong-eval-order but do understand -std=c++17), and they use
> the same order as GCC 7.3.0.

Unsurprising, since GCC 5 and GCC 6 were released before the evaluation order
rules changed in the C++17 drafts. Understanding the -std=c++17 option doesn't
mean they conform to the final standard and this evaluation order is how GCC
always did it.