https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79534
Richard Biener changed:
What|Removed |Added
Target Milestone|7.3 |7.4
--- Comment #15 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79534
Richard Biener changed:
What|Removed |Added
Target Milestone|7.2 |7.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79534
Richard Biener changed:
What|Removed |Added
Target Milestone|7.2 |7.3
--- Comment #15 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79534
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|7.0 |7.2
--- Comment #14 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79534
--- Comment #13 from Brian Rzycki ---
James, if you develop any new ifcvt any patches you'd like to test on my full
source base I'd be happy to help. The code is very branchy and in some cases
have up to 4 nested if/else pairs. There are a couple
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79534
--- Comment #12 from James Greenhalgh ---
So while there's nothing buggy about the if-conversion which causes the
performance issue, it does show an interesting missed optimization that ifcvt
can't handle.
We make the transform through find_if_c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79534
--- Comment #11 from Brian Rzycki ---
HI James, if you don't see any major regressions and some good uplifts I
understand if this case is considered marginal. From my perspective I think
it's best to close this ticket and move on to more pressing
