From: FX Coudert <fxcoudert@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: iain@sandoe.co.uk, Eric Gallager <egall@gwmail.gwu.edu>
Subject: Re: [PATCH] jit: Ensure ssize_t is defined.
Date: Thu, 2 May 2024 21:48:15 +0200 [thread overview]
Message-ID: <2E73A53A-AF7C-4696-BD97-C7DA47F6DF94@gmail.com> (raw)
I’d like to ping the patch at https://gcc.gnu.org/pipermail/gcc-patches/2024-January/644134.html
The original proposal by Iain was:
diff --git a/gcc/jit/libgccjit.h b/gcc/jit/libgccjit.h
index 235cab053e0..db4f27a48bf 100644
--- a/gcc/jit/libgccjit.h
+++ b/gcc/jit/libgccjit.h
@@ -21,6 +21,9 @@ along with GCC; see the file COPYING3. If not see
#define LIBGCCJIT_H
#include <stdio.h>
+#if __has_include(<sys/types.h>)
+# include <sys/types.h> /* For ssize_t. */
+#endif
#ifdef __cplusplus
extern "C" {
but it seems we can’t use __has_include. However, other code in GCC treats <sys/types.h> as available on all targets. See unconditional inclusion in gcc/system.h and gcc/tsystem.h. The latter even says:
/* All systems have this header. */
#include <sys/types.h>
So: would an unconditional inclusion be suitable? I’ve tested on linux and darwin with no issues:
diff --git a/gcc/jit/libgccjit.h b/gcc/jit/libgccjit.h
index 74e847b2dec..cbe0f70abee 100644
--- a/gcc/jit/libgccjit.h
+++ b/gcc/jit/libgccjit.h
@@ -21,6 +21,7 @@ along with GCC; see the file COPYING3. If not see
#define LIBGCCJIT_H
#include <stdio.h>
+#include <sys/types.h>
#ifdef __cplusplus
extern "C” {
Thanks,
FX
next reply other threads:[~2024-05-02 19:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 19:48 FX Coudert [this message]
2024-05-11 15:16 ` FX Coudert
2024-05-26 15:35 ` FX Coudert
2024-06-01 16:44 ` FX Coudert
2024-06-11 6:06 ` FX Coudert
2024-06-11 7:27 ` Richard Biener
2024-06-11 7:44 ` Jakub Jelinek
2024-06-11 8:03 ` Iain Sandoe
2024-06-11 8:04 ` Richard Biener
2024-06-11 8:06 ` Richard Biener
2024-06-11 8:16 ` Iain Sandoe
2024-06-11 8:34 ` Andreas Schwab
2024-06-11 8:20 ` Jakub Jelinek
2024-06-11 8:21 ` Andreas Schwab
2024-06-27 17:08 ` FX Coudert
2024-06-28 6:17 ` Richard Biener
2024-06-28 7:15 ` FX Coudert
2024-09-07 17:35 ` FX Coudert
2024-09-18 10:28 ` FX Coudert
2024-09-18 10:53 ` Richard Biener
2024-09-18 17:53 ` FX Coudert
2024-06-11 8:21 ` FX Coudert
2024-06-11 7:20 ` Xi Ruoyao
-- strict thread matches above, loose matches on Subject: below --
2024-01-28 11:44 Iain Sandoe
2024-01-28 21:25 ` Eric Gallager
2024-01-28 23:13 ` Iain Sandoe
2024-01-29 11:26 ` Iain Sandoe
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2E73A53A-AF7C-4696-BD97-C7DA47F6DF94@gmail.com \
--to=fxcoudert@gmail.com \
--cc=egall@gwmail.gwu.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).