From: Jon Turney <jon.turney@dronecode.org.uk>
To: joel@rtems.org, Newlib <newlib@sourceware.org>,
Chris Johns <chrisj@rtems.org>
Subject: Re: Include FD_SETSIZE on RTEMS to 256
Date: Wed, 13 Mar 2024 14:21:38 +0000 [thread overview]
Message-ID: <9514182a-f513-4296-8178-43b5274abb7f@dronecode.org.uk> (raw)
In-Reply-To: <CAF9ehCU8MjXkbzm7NzMdtzcqT20hEJEw74rdEaqxJWBWHXO56w@mail.gmail.com>
On 28/02/2024 23:02, Joel Sherrill wrote:
> Hi
>
> The attached patch changes FD_SETSIZE from 64 to 256 for RTEMS.
>
> Is it OK to apply?
>
This uses the preprocessor directive '#elifdef',
It seems like support for that was added in gcc 12.
next prev parent reply other threads:[~2024-03-13 14:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 23:02 Joel Sherrill
2024-02-29 6:29 ` Sebastian Huber
2024-02-29 6:31 ` Sebastian Huber
2024-02-29 14:24 ` Joel Sherrill
2024-03-11 14:50 ` Joel Sherrill
2024-03-12 17:13 ` Corinna Vinschen
2024-03-13 14:21 ` Jon Turney [this message]
2024-03-13 14:35 ` Joel Sherrill
2024-03-13 15:02 ` Corinna Vinschen
2024-03-13 16:03 ` Joel Sherrill
2024-03-13 16:33 ` Joel Sherrill
2024-03-13 17:06 ` Corinna Vinschen
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=9514182a-f513-4296-8178-43b5274abb7f@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=chrisj@rtems.org \
--cc=joel@rtems.org \
--cc=newlib@sourceware.org \
/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).