From: Andreas Schwab <schwab@suse.de>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: Richard Biener <rguenther@suse.de>,
Jakub Jelinek <jakub@redhat.com>,
FX Coudert <fxcoudert@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
dmalcolm@redhat.com, Eric Gallager <egall@gwmail.gwu.edu>,
josmyers@redhat.com
Subject: Re: [PATCH] jit: Ensure ssize_t is defined.
Date: Tue, 11 Jun 2024 10:34:03 +0200 [thread overview]
Message-ID: <mvmmsnrri84.fsf@suse.de> (raw)
In-Reply-To: <FF05C582-E0EB-4C09-8D12-2C1547CE3A4D@sandoe.co.uk> (Iain Sandoe's message of "Tue, 11 Jun 2024 09:16:50 +0100")
On Jun 11 2024, Iain Sandoe wrote:
> well, afaict, all the code is c++ and we are building with a std >= 11, so that
> presumes c99 support.
The C standard does not define ssize_t at all, it is only part of POSIX.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2024-06-11 8:34 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 [this message]
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
-- 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=mvmmsnrri84.fsf@suse.de \
--to=schwab@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 \
--cc=rguenther@suse.de \
/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).