[Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore

2020-06-11 Thread kito at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95252 Kito Cheng changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore

2020-06-02 Thread kito at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95252 Kito Cheng changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #9 from Kito Cheng

[Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore

2020-06-01 Thread kito.cheng at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95252 Kito Cheng changed: What|Removed |Added CC||kito.cheng at gmail dot com --- Comment #8

[Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore

2020-05-28 Thread wilson at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95252 --- Comment #7 from Jim Wilson --- I've got 3 new g++ testsuite failures. So we might still need an exact list of USEs. I hadn't thought about RVE. That will have to be checked also. RV32/RV64 shouldn't matter, as the mode in the USEs

[Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore

2020-05-27 Thread kito at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95252 --- Comment #6 from Kito Cheng --- Oh, seems like add uses is enough, exact pattern might add about ~200 line to md file include RV32E/RV32/RV64 I guess.

[Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore

2020-05-27 Thread wilson at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95252 --- Comment #5 from Jim Wilson --- Created attachment 48625 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48625=edit add uses to gpr_save pattern the code using MASK_SAVE_RESTORE is just for testing purposes unfinished, adds 3 new g++

[Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore

2020-05-27 Thread wilson at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95252 --- Comment #4 from Jim Wilson --- Created attachment 48624 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48624=edit disable reg rename when -msave-restore the code using MASK_SAVE_RESTORE is just for testing purposes

[Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore

2020-05-27 Thread wilson at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95252 --- Comment #3 from Jim Wilson --- I tried both. Turning off register naming works. It gives a code size decrease of about 0.003% for the libraries I looked at which can be ignored. This probably also reduces performance; I didn't check that.

[Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore

2020-05-26 Thread kito at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95252 --- Comment #2 from Kito Cheng --- Hi Jim: Not sure which way you will try first, maybe Monk or me can try to fix this by add bunch of pattern of gpr_save/gpr_restore to model set/use register correctly?

[Bug target/95252] testcase gcc.dg/torture/pr67916.c failure when testing with -msave-restore

2020-05-25 Thread wilson at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95252 Jim Wilson changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|