public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: FX Coudert <fxcoudert@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Jakub Jelinek <jakub@redhat.com>,
	 dmalcolm@redhat.com, Iain Sandoe <iain@sandoe.co.uk>,
	 Eric Gallager <egall@gwmail.gwu.edu>,
	josmyers@redhat.com
Subject: Re: [PATCH] jit: Ensure ssize_t is defined.
Date: Wed, 18 Sep 2024 12:53:45 +0200 (CEST)	[thread overview]
Message-ID: <60s5srq6-35pp-2n20-3sp6-q811oq7sq4or@fhfr.qr> (raw)
In-Reply-To: <4824E9EE-E18C-4EB5-9E00-D619100F3F60@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]

On Wed, 18 Sep 2024, FX Coudert wrote:

> Can I please get an approval on that one? It’s been there since January, I’ve amended it following review, but cannot get a definite ok. It is five lines.
> 
> Bootstrapped on x86_64-apple-darwin23. OK to push?

OK.

> FX
> 
> 
> > Le 7 sept. 2024 à 19:35, FX Coudert <fxcoudert@gmail.com> a écrit :
> > 
> > ping**many on this patch, originally from January.
> > In latest round, Richard suggested that David should have the last say, I’ve never had any response.
> > 
> > 
> >> Le 27 juin 2024 à 19:08, FX Coudert <fxcoudert@gmail.com> a écrit :
> >> 
> >> Among the review comments from the last round, Jakub suggested:
> >> 
> >>> Perhaps libgccjit.h could use
> >>> #ifdef __has_include
> >>> #if __has_include (<sys/types.h>)
> >>> #include <sys/types.h>
> >>> #endif
> >>> #endif
> >>> instead of just #include <sys/types.h>.
> >> 
> >> I’m not sure it’s necessary since other headers treat <sys/types.h> as always available, but I suppose it can’t hurt. So here is a revised patch as suggested.
> >> 
> >> 
> >> Bootstrapped on x86_64-apple-darwin23. OK to push?
> >> 
> >> FX
> 
> 

-- 
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH,
Frankenstrasse 146, 90461 Nuernberg, Germany;
GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)

  reply	other threads:[~2024-09-18 10:53 UTC|newest]

Thread overview: 27+ 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-09-07 17:35           ` FX Coudert
2024-09-18 10:28             ` FX Coudert
2024-09-18 10:53               ` Richard Biener [this message]
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=60s5srq6-35pp-2n20-3sp6-q811oq7sq4or@fhfr.qr \
    --to=rguenther@suse.de \
    --cc=dmalcolm@redhat.com \
    --cc=egall@gwmail.gwu.edu \
    --cc=fxcoudert@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=jakub@redhat.com \
    --cc=josmyers@redhat.com \
    /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).