Andrew Pinski via Gcc <[email protected]> writes: > It has been a few months since I last made the proposal of deprecating > IA64 and it seems like not much has changed. Nobody has stepped up. > There has been a few fixes but still no testresults for the trunk > sent. (there was one sent for GCC 15.1.0 and 15.2.0).
I just want to say that my remarks from before [0] stand. I don't think we should support a target which is not in upstream glibc or the Linux kernel (where it is for those) unless there is movement to it landing back in. So +1. There were some fixes sent though but it doesn't change that it needs someone properly involved in GCC regularly sending test results and fixing bugs, not just a drive-by. > Also at the same time I am also proposing to deprecate selective > scheduling since it is not enabled by default except on ia64. > Selective scheduling is broken for most other targets producing either > ICEs or wrong code. > Removing selective scheduling for GCC 17 would allow for some cleanups > in CFGhooks and maybe other places too. > I can't speak on this part, so I won't, other than saying it seems to be a rife target for the fuzzers. [0] https://inbox.sourceware.org/gcc-patches/[email protected]/ > Thanks, > Andrew sam
