https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97313
Martin Liška changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97313
--- Comment #5 from Vladimir Makarov ---
(In reply to Martin Liška from comment #4)
> Thank you Vladimir for the fix.
> Can we close it now?
There are no complaints about the patch for more a week. So I guess the PR can
be closed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97313
--- Comment #4 from Martin Liška ---
Thank you Vladimir for the fix.
Can we close it now?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97313
--- Comment #3 from CVS Commits ---
The releases/gcc-10 branch has been updated by Vladimir Makarov
:
https://gcc.gnu.org/g:70a66ff0228277b4dd89263a663c0a87eb5d782f
commit r10-8874-g70a66ff0228277b4dd89263a663c0a87eb5d782f
Author: Vladimir N. M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97313
--- Comment #2 from CVS Commits ---
The master branch has been updated by Vladimir Makarov :
https://gcc.gnu.org/g:bb37ad8cc0fc937c7afcdab471e5d65d176041c3
commit r11-3758-gbb37ad8cc0fc937c7afcdab471e5d65d176041c3
Author: Vladimir N. Makarov
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97313
--- Comment #1 from Vladimir Makarov ---
Thank you for reporting this. I am trying to find the best place to fix this:
either in memory subreg elimination or in match_reload itself. I hope the fix
will be ready tomorrow.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97313
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2020-10-07
Known to work|
