Testsuite: various changes to allow native light runtime runs

This commit brings various changes that allow the execution of the
testsuite for a native target with a light runtime:
 - Fix light runtime detection pattern in RuntimeInfo;
 - Add missing RTS_ZFP filters for native only tests that use lagnuage
   features not available in the light runtime;
 - Remove exit code checking on native light runtime program execution,
   as the programs do not set the exit status code, often resulting in
   it being non-zero despite a normal termination of the program.

This is in preparation of the introduction of CCG testing.

Author: leocreuse

testsuite/Qualif/Appendix/Testsuite/Selftest/assert-failure/test.opt

@@ -0,0 +1 @@
+native,RTS_ZFP DEAD Test assumes bin file available on native platform

testsuite/SUITE/control.py

@@ -252,7 +252,10 @@ def __init__(self, runtime_name=None):
         elif self.runtime_name.startswith('zfp'):
             self.has_light_runtime = True
             self.has_exception_propagation = False
-        elif self.runtime_name.startswith('light-'):
+        elif (
+            self.runtime_name == "light" 
+            or self.runtime_name.startswith('light-')
+        ):
             self.has_light_runtime = True
             self.has_exception_propagation = False
         elif self.runtime_name == 'kernel':

testsuite/SUITE/tutils.py

@@ -852,6 +852,14 @@ def run_cov_program(executable, out=None, env=None, exec_args=None,
         # failing. Redirecting the standard input to /dev/null works around
         # this issue.
         inp = DEVNULL
+    else:
+        # Native programs using a light runtime can't set the exit code, and
+        # will often terminate with a non-zero status code even though nothing
+        # went wrong. There is thus no point in checking the exit code in this
+        # configuration.
+        register_failure = (
+            register_failure and not RUNTIME_INFO.has_light_runtime
+        )
 
     args.append(executable)
     args.extend(exec_args)

testsuite/tests/C/stmt/NA28-015-default-return/test.opt

@@ -1 +1,2 @@
-!x86-linux,!x86_64-linux DEAD test relies on passing command line arguments
+!x86-linux,!x86_64-linux DEAD test relies on passing command line arguments
+RTS_ZFP DEAD test relies on bin-file dump channel

testsuite/tests/M724-035-eh-warnings/test.opt

@@ -1,2 +1,2 @@
 ALL DEAD
-native
+native,!RTS_ZFP

testsuite/tests/U219-010-ali-entry-guard-sloc/test.opt

@@ -1 +1,2 @@
 !native DEAD Uses full runtime only constructs
+RTS_ZFP DEAD Uses full runtime only constructs

testsuite/tests/U901-029-estamps/test.opt

@@ -1 +1,2 @@
 src-traces,!native DEAD checking trace stamp, no way to get from BB programs
+native,RTS_ZFP DEAD checking trace stamp, no way to get it from light runtime

testsuite/tests/V309-017-setup-config/test.opt

@@ -1,4 +1,6 @@
 --  This test needs to check that --dump-channel is properly handled in a
 --  typical gnatcov usage workflow. To do this, it needs multiple dump channels
---  to be supported, i.e. a native platform (bin-file and base64-stdout).
+--  to be supported, i.e. a native platform (bin-file and base64-stdout), and
+--  a full runtime.
 !native DEAD
+RTS_ZFP DEAD

testsuite/tests/instr-cov/bin_file_tunings/test.opt

@@ -1 +1,2 @@
 !native DEAD Test specific to source trace binary files directly produced by automatic main instrumentation
+RTS_ZFP DEAD Test required bin-file dump channel to be available

testsuite/tests/instr-cov/default_dump_channel/test.opt

@@ -1,2 +1,3 @@
 !src-traces DEAD Checks a feature specific to the instrumenter
 !native     DEAD Checks the default dump channel (bin-file, native only)
+RTS_ZFP     DEAD requires bin-file available