On 6/14/19 6:26 PM, Jason Duerstock wrote: > I volunteer to be maintainer for ia64. So the first step would be to start your assignment paperwork with the FSF. Without it we can't accept non-trivial contributions/fixes from you.
Contact ass...@gnu.org to get a past and future copyright assignment for GCC. Depending on your precise situation you may also need an employer disclaimer. The second step (and you might want to work with Jakub Jermar) would be to set up a bootstrap & regression test bot of some kind that posts its results to gcc-testresu...@gcc.gnu.org. We realize ia64 hardware can be slow, so we certainly will be understanding if results aren't posted as regularly as other platforms. But they're still helpful. Finally, starting to work through some of the existing target specific issues would be helpful. I'm sure there's some in BZ and we know there's some significant problems with how the ia64 port interacts with the scheduler and the qsort checking (which ultimately prevent linux kernels from building). I'm sure folks here are willing to help as you get familiar with the codebase and start to look at issues. Jeff
