Hi Joel,

On Sun, Aug 24, 2025 at 08:28:29AM -0500, Joel Sherrill wrote:
> On Sun, Aug 24, 2025, 7:41 AM Mark Wielaard <m...@klomp.org> wrote:
> > On Wed, Aug 13, 2025 at 08:53:44AM +0200, Richard Biener via Gcc wrote:
> > > That said, I'd like to move away from gcc-testresults as a vetting
> > > tool to something more modern.
> >
> > If the port has a (qemu) emulator we could create a x86_64 container
> > for it and run it once a month/week on one of the faster
> > builder.sourceware.org workers.
> >
> > https://sourceware.org/cgit/builder/tree/README
> > https://sourceware.org/cgit/builder/tree/builder/containers
> >
> > Are there any ports that can be tested that way? And does someone have
> > a description (or script) of such a (cross) build that we could turn
> > into a x86_64 container build?
>
> For which architectures? We might have one if RTEMS ever ran on it.

I think for architectures where there are at least some people who
would fix issues pointed out by the builders and/or where the release
maintainers want to know if the port is not broken, showing it at
least builds.

Cheers,

Mark

Reply via email to