From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: Issue: #include <stdio.h> shall not cause intmax_t to be defined
Date: Wed, 4 May 2022 10:37:35 +0200 [thread overview]
Message-ID: <YnI7T8LJzMUOSnEr@calimero.vinschen.de> (raw)
In-Reply-To: <d5849bb6-123e-109e-184e-9fb9cdec78af@embedded-brains.de>
On May 4 09:59, Sebastian Huber wrote:
> On 03/05/2022 19:00, Corinna Vinschen wrote:
> > On Apr 27 00:41, Pavel M wrote:
> > > Hi all,
> > >
> > > Issue: #include <stdio.h> shall not cause intmax_t to be defined. However,
> > > now it causes. This is because now <stdio.h> includes <sys/types.h>, which
> > > includes <sys/_stdint.h>.
> > > Note: per C11 the types intmax_t and uintmax_t defined in the header
> > > <stdint.h>, and <stdint.h> is not included in <stdio.h>.
> > > Consider fixing.
> > I pushed a patch to fix this.
>
> In FreeBSD, <sys/types.h> provides the stdint.h types. Could we bring back
> this with
Is that with FreeeBSD only, or is that with BSDs in general?
> #if __BSD_VISIBLE
> #include <machine/endian.h>
> #include <sys/select.h>
> #include <sys/_stdint.h>
> # define physadr physadr_t
> # define quad quad_t
>
> ?
>
> In addition, the C11 header files should not include <sys/types.h>.
Which files are these exactly? Feel free to submit patches.
Corinna
next prev parent reply other threads:[~2022-05-04 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 21:41 Pavel M
2022-05-03 17:00 ` Corinna Vinschen
2022-05-04 7:59 ` Sebastian Huber
2022-05-04 8:37 ` Corinna Vinschen [this message]
2022-05-04 8:41 ` Sebastian Huber
2022-05-04 8:54 ` Corinna Vinschen
2022-05-04 9:02 ` Sebastian Huber
2022-05-04 13:12 ` Corinna Vinschen
2022-05-05 16:15 ` Pavel M
2022-05-06 9:14 ` 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=YnI7T8LJzMUOSnEr@calimero.vinschen.de \
--to=vinschen@redhat.com \
--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).