Re: ping: COBOL: testsuite and running NIST85

2025-04-10 Thread Jakub Jelinek
On Mon, Apr 07, 2025 at 09:30:59AM +0200, Richard Biener wrote: > On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote: > > My question stands on integrating COBOLworx' UAT as-is for now > > (Copyright is all on FSF; built automatically [it is autoconf, which is > > a requirement for VCS checkouts],

Re: ping: COBOL: testsuite and running NIST85

2025-04-07 Thread Richard Biener
On Mon, Apr 7, 2025 at 9:41 AM Simon Sobisch wrote: > > > > Am 07.04.2025 um 09:30 schrieb Richard Biener: > > On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote: > >> > >> My question stands on integrating COBOLworx' UAT as-is for now > >> (Copyright is all on FSF; built automatically [it is aut

Re: ping: COBOL: testsuite and running NIST85

2025-04-07 Thread Simon Sobisch
Am 07.04.2025 um 09:36 schrieb Jakub Jelinek: On Mon, Apr 07, 2025 at 09:30:59AM +0200, Richard Biener wrote: On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote: My question stands on integrating COBOLworx' UAT as-is for now (Copyright is all on FSF; built automatically [it is autoconf, which

Re: ping: COBOL: testsuite and running NIST85

2025-04-07 Thread Simon Sobisch
Am 07.04.2025 um 09:30 schrieb Richard Biener: On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote: My question stands on integrating COBOLworx' UAT as-is for now (Copyright is all on FSF; built automatically [it is autoconf, which is a requirement for VCS checkouts], possibly also hooked in

Re: ping: COBOL: testsuite and running NIST85

2025-04-07 Thread Richard Biener
On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote: > > My question stands on integrating COBOLworx' UAT as-is for now > (Copyright is all on FSF; built automatically [it is autoconf, which is > a requirement for VCS checkouts], possibly also hooked into the current > test target) - with the goal