From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: newlib@sourceware.org
Subject: Re: Issue: #include <stdio.h> shall not cause intmax_t to be defined
Date: Wed, 4 May 2022 09:59:54 +0200 [thread overview]
Message-ID: <d5849bb6-123e-109e-184e-9fb9cdec78af@embedded-brains.de> (raw)
In-Reply-To: <YnFfoKv1IYoKLNv1@calimero.vinschen.de>
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
#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>.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2022-05-04 7:59 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 [this message]
2022-05-04 8:37 ` Corinna Vinschen
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=d5849bb6-123e-109e-184e-9fb9cdec78af@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--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).