[Bug tree-optimization/105329] Bogus restrict warning when assigning 1-char string literal to std::string

[amacleod at redhat dot com]

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

--- Comment #2 from Andrew Macleod <amacleod at redhat dot com> ---
The problem goes away if we use --param=evrp-mode-legacy.  Ranger picks up a
few more things and we eliminate a couple of latter comparisons which in turn
affect threading, etc etc. and we present the restrict pass with something
different  that causes issues.  

I'm in the middle of analyzing it and will post the results when I'm done.