public inbox for
help / color / mirror / Atom feed
From: Adhemerval Zanella <>
Subject: [glibc/release/2.36/master] Add compile_c_snippet
Date: Wed, 24 Aug 2022 13:05:59 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=0062e7dd1c3674ece2daca53a898badd28b60421

commit 0062e7dd1c3674ece2daca53a898badd28b60421
Author: Adhemerval Zanella <>
Date:   Wed Aug 10 16:24:06 2022 -0300 Add compile_c_snippet
    It might be used on tests to check if a snippet build with the provided
    compiler and flags.
    Reviewed-by: Florian Weimer <>
    (cherry picked from commit 841afa116e32b3c7195475769c26bf46fd870d32)

 scripts/ | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/scripts/ b/scripts/
index 43ab58ffe2..36d204c9b0 100644
--- a/scripts/
+++ b/scripts/
@@ -17,6 +17,7 @@
 # License along with the GNU C Library; if not, see
 # <>.
+import collections
 import os.path
 import re
 import subprocess
@@ -173,3 +174,21 @@ def compare_macro_consts(source_1, source_2, cc, macro_re, exclude_re=None,
             if not allow_extra_2:
                 ret = 1
     return ret
+CompileResult = collections.namedtuple("CompileResult", "returncode output")
+def compile_c_snippet(snippet, cc, extra_cc_args=''):
+    """Compile and return whether the SNIPPET can be build with CC along
+       EXTRA_CC_ARGS compiler flags.  Return a CompileResult with RETURNCODE
+       being 0 for success, or the failure value and the compiler output.
+    """
+    with tempfile.TemporaryDirectory() as temp_dir:
+        c_file_name = os.path.join(temp_dir, 'test.c')
+        obj_file_name = os.path.join(temp_dir, 'test.o')
+        with open(c_file_name, 'w') as c_file:
+            c_file.write(snippet + '\n')
+        cmd = cc.split() + extra_cc_args.split() + ['-c', '-o', obj_file_name,
+                c_file_name]
+        r =, check=False, stdout=subprocess.PIPE,
+                stderr=subprocess.STDOUT)
+        return CompileResult(r.returncode, r.stdout)

                 reply	other threads:[~2022-08-24 13:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).