[Bug rtl-optimization/80352] Improper reload of operands with equiv pseudo

2017-06-16 Thread ramana at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80352 Ramana Radhakrishnan changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug rtl-optimization/80352] Improper reload of operands with equiv pseudo

2017-04-26 Thread thopre01 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80352 --- Comment #5 from Thomas Preud'homme --- FWIW, I've configured GCC with --target=arm-none-eabi --with-cpu=cortex-m7 --with-mode=thumb and then ran make all-gcc. I think it would work equally well without the cpu and mode given that these are gi

[Bug rtl-optimization/80352] Improper reload of operands with equiv pseudo

2017-04-26 Thread thopre01 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80352 --- Comment #4 from Thomas Preud'homme --- (In reply to Vladimir Makarov from comment #1) > Thomas, it seems from your description the problem really exists. I tried > to reproduce the problem with the test you provided but I've failed. I used

[Bug rtl-optimization/80352] Improper reload of operands with equiv pseudo

2017-04-11 Thread vmakarov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80352 --- Comment #3 from Vladimir Makarov --- (In reply to Vladimir Makarov from comment #2) > Thank you for the report. I'll investigate the problem. A few hours ago > I've committed an additional patch. It might solve the problem. I'll check > i

[Bug rtl-optimization/80352] Improper reload of operands with equiv pseudo

2017-04-11 Thread vmakarov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80352 --- Comment #2 from Vladimir Makarov --- Thank you for the report. I'll investigate the problem. A few hours ago I've committed an additional patch. It might solve the problem. I'll check it.

[Bug rtl-optimization/80352] Improper reload of operands with equiv pseudo

2017-04-11 Thread vmakarov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80352 --- Comment #1 from Vladimir Makarov --- Thomas, it seems from your description the problem really exists. I tried to reproduce the problem with the test you provided but I've failed. I used today trunk. Could you provide more info (may be -m