public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: FX Coudert <fxcoudert@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	dmalcolm@redhat.com
Cc: Iain Sandoe <iain@sandoe.co.uk>, Eric Gallager <egall@gwmail.gwu.edu>
Subject: Re: [PATCH] jit: Ensure ssize_t is defined.
Date: Tue, 11 Jun 2024 15:20:29 +0800	[thread overview]
Message-ID: <e10a1cc456e712212ac7b780ccb1db67886c2ef0.camel@xry111.site> (raw)
In-Reply-To: <EC94C74D-2A87-445C-B64D-A2EC4DAD0834@gmail.com>

On Sat, 2024-05-11 at 17:16 +0200, FX Coudert wrote:
> 	* libgccjit.h: Include <sys/types.h>

Per the C standard size_t should be provided by stddef.h.

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  parent reply	other threads:[~2024-06-11  7:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 19:48 FX Coudert
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-06-11  8:21       ` FX Coudert
2024-06-11  7:20   ` Xi Ruoyao [this message]
  -- 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=e10a1cc456e712212ac7b780ccb1db67886c2ef0.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=dmalcolm@redhat.com \
    --cc=egall@gwmail.gwu.edu \
    --cc=fxcoudert@gmail.com \
    --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).