On Wed, 10 Dec 2025, 01:49 Frank Scheiner via Gcc, <[email protected]> wrote:
> Dear Andrew, all, > > On 09.12.25 21:15, Andrew Pinski via Gcc wrote: > > 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 don't really follow. But maybe I misunderstood that thread you spoke of, > so I re-read the whole thread. > > In [1] you wrote: > > > I also vote to have a testresults for the target at least once a year. > > [1]: https://gcc.gnu.org/pipermail/gcc/2025-August/246502.html > > Granted, the last result I posted in August was not from trunk, but from > the current stable version; also for comparison reasons with existing > test results it made sense to target GCC 15.1.0 and 15.2.0 instead of > trunk. > This only tells us whether 15.2.0 works, which is probably the same answer as whether 15.1.0 works. Testing the official releases is better than nothing, but why aren't you posting test results for the branch *before* a release, so that if something is broken it can get fixed before the release? But what's really needed is to know whether the trunk works, because that's where most changes happen. If you don't test trunk then some change that breaks your target could go unnoticed on trunk, and you'd be stuck on 15.x forever. It's also possible (but less likely) that if nobody notices the trunk change breaks ia64 then the change might even get backported to the stable 15.x branch. If you're happy to stay on 15.x forever, you don't need to test trunk, and you shouldn't care if the target is removed from trunk. But if you want the target to remain on trunk, you need to report test results for trunk.
