[Bug middle-end/68677] Sibcall doesn't work on function with no return

2015-12-03 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68677 Andrew Pinski changed: What|Removed |Added Resolution|WONTFIX |DUPLICATE --- Comment #4 from Andrew Pin

[Bug middle-end/68677] Sibcall doesn't work on function with no return

2015-12-03 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68677 H.J. Lu changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug middle-end/68677] Sibcall doesn't work on function with no return

2015-12-03 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68677 --- Comment #2 from Jakub Jelinek --- I believe this is intentional and has been discussed in the past. E.g. one of the often used noreturn functions is abort and its callers, in that case we better not sibcall to that, as it will be harder to fi

[Bug middle-end/68677] Sibcall doesn't work on function with no return

2015-12-03 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68677 --- Comment #1 from Richard Biener --- It's a feature for debugging of abort()-like calls. And in this case it's a tailcall as well (which is probably what you are after).