public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/31749] New: endian.h should define uint16_t, uint32_t, and uint64_t
@ 2024-05-17 4:35 collin.funk1 at gmail dot com
2024-05-18 9:33 ` [Bug libc/31749] " bruno at clisp dot org
2024-06-11 19:11 ` fweimer at redhat dot com
0 siblings, 2 replies; 3+ messages in thread
From: collin.funk1 at gmail dot com @ 2024-05-17 4:35 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31749
Bug ID: 31749
Summary: endian.h should define uint16_t, uint32_t, and
uint64_t
Product: glibc
Version: 2.39
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: collin.funk1 at gmail dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Hello,
Not sure if it is too soon to care about POSIX revision 8 since it isn't
official yet.
The next revision will likely require <endian.h> to define uint16_t, uint32_t,
or uint64_t. Optionally, it may make all symbols from <stdint.h> visible [1].
I was writing a Gnulib module using that specification and noticed that glibc
doesn't define those types. My system uses glibc 2.39.
Here is a snippet from the test case I was writing for Gnulib. Feel free to use
it if it is of any help:
$ cat main.c
#define _GNU_SOURCE 1
#include <endian.h>
static_assert (LITTLE_ENDIAN != BIG_ENDIAN);
static_assert (BYTE_ORDER == LITTLE_ENDIAN || BYTE_ORDER == BIG_ENDIAN);
uint16_t t1;
uint32_t t2;
uint64_t t3;
int
main (void)
{
return 0;
}
$ gcc -std=c23 main.c
main.c:8:1: error: unknown type name ‘uint16_t’
8 | uint16_t t1;
| ^~~~~~~~
main.c:4:1: note: ‘uint16_t’ is defined in header ‘<stdint.h>’; this is
probably fixable by adding ‘#include <stdint.h>’
3 | #include <endian.h>
+++ |+#include <stdint.h>
[...]
Thanks!
[1] https://austingroupbugs.net/view.php?id=162
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/31749] endian.h should define uint16_t, uint32_t, and uint64_t
2024-05-17 4:35 [Bug libc/31749] New: endian.h should define uint16_t, uint32_t, and uint64_t collin.funk1 at gmail dot com
@ 2024-05-18 9:33 ` bruno at clisp dot org
2024-06-11 19:11 ` fweimer at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: bruno at clisp dot org @ 2024-05-18 9:33 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31749
Bruno Haible <bruno at clisp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bruno at clisp dot org
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/31749] endian.h should define uint16_t, uint32_t, and uint64_t
2024-05-17 4:35 [Bug libc/31749] New: endian.h should define uint16_t, uint32_t, and uint64_t collin.funk1 at gmail dot com
2024-05-18 9:33 ` [Bug libc/31749] " bruno at clisp dot org
@ 2024-06-11 19:11 ` fweimer at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: fweimer at redhat dot com @ 2024-06-11 19:11 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31749
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
CC| |fweimer at redhat dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-06-11 19:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-17 4:35 [Bug libc/31749] New: endian.h should define uint16_t, uint32_t, and uint64_t collin.funk1 at gmail dot com
2024-05-18 9:33 ` [Bug libc/31749] " bruno at clisp dot org
2024-06-11 19:11 ` fweimer at redhat dot com
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).