This came up on IRC this morning and we talked a bit on the patchwork call this morning. I'm not really sure what the right answer is here, but it seems at least reasonable to talk about -- we've got a lot more testing these days are we've been somewhat reasonable about following the release stages. Either way it looks like a mailing list discussion and this seems like the easiest way to start it.
I figured it'd be best to start with just rv64gc, as that's the target that is widley used by distros and has hardware to test on. Hopefully at some point we'll add a more exciting target, but it seems safer to start with something small. --- htdocs/gcc-15/criteria.html | 1 + 1 file changed, 1 insertion(+) diff --git a/htdocs/gcc-15/criteria.html b/htdocs/gcc-15/criteria.html index 7faa54e9..25ea7e61 100644 --- a/htdocs/gcc-15/criteria.html +++ b/htdocs/gcc-15/criteria.html @@ -125,6 +125,7 @@ application testing.</p> <li>i686-mingw32</li> <li>s390x-linux-gnu</li> <li>mips64-linux-gnu</li> +<li>riscv64-linux-gnu (for rv64gc)</li> </ul> <h1>Code Quality and Compilation Time</h1> -- 2.45.2
