[Bug tree-optimization/71990] Function multiversioning prohibits inlining

2023-05-22 Thread vanyacpp at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71990 Ivan Sorokin changed: What|Removed |Added CC||vanyacpp at gmail dot com --- Comment #5

[Bug tree-optimization/71990] Function multiversioning prohibits inlining

2016-07-25 Thread sgunderson at bigfoot dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71990 --- Comment #4 from sgunderson at bigfoot dot com --- OK, so it would have to be a special kind of cloning, not the one you can do yourself from code as of today? As a user, I suppose there's no really good way of dealing with this currently, rig

[Bug tree-optimization/71990] Function multiversioning prohibits inlining

2016-07-25 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71990 --- Comment #3 from Richard Biener --- (In reply to sgunderson from comment #2) > Would pushing the mv automatically upwards into callers really help? There's > still no way that I can see to inline the function; I mean, pushing upwards > is what

[Bug tree-optimization/71990] Function multiversioning prohibits inlining

2016-07-25 Thread sgunderson at bigfoot dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71990 --- Comment #2 from sgunderson at bigfoot dot com --- Would pushing the mv automatically upwards into callers really help? There's still no way that I can see to inline the function; I mean, pushing upwards is what I've been trying to do here manu

[Bug tree-optimization/71990] Function multiversioning prohibits inlining

2016-07-25 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71990 Richard Biener changed: What|Removed |Added CC||hubicka at gcc dot gnu.org --- Comment