Fixes; Document remaining stdint.h types
cover Fixes; Document remaining stdint.h types
Hi Michael,
Here are a few fixes (including one removing .br), and then the remaining stdint types.
Cheers,
Alex
Alejandro Colomar (16):
malloc_get_state.3: ffix
system_data_types.7: srcfix
system_data_types.7: srcfix
system_data_types.7: srcfix
system_data_types.7: Add int_fastN_t family of types int_fast8_t.3, int_fast16_t.3, int_fast32_t.3, int_fast64_t.3,
int_fastN_t.3: New links to system_data_types(7)
system_data_types.7: Add uint_fastN_t family of types uint_fast8_t.3, uint_fast16_t.3, uint_fast32_t.3, uint_fast64_t.3,
uint_fastN_t.3: New links to system_data_types(7)
system_data_types.7: Add int_leastN_t family of types int_least8_t.3, int_least16_t.3, int_least32_t.3, int_least64_t.3,
int_leastN_t.3: New links to system_data_types(7)
system_data_types.7: Add uint_leastN_t family of types uint_least8_t.3, uint_least16_t.3, uint_least32_t.3, uint_least64_t.3,
uint_leastN_t.3: New links to system_data_types(7)
system_data_types.7: Add 'intptr_t'
intptr_t.3: New link to system_data_types(7) system_data_types.7: Add 'uintptr_t'
uintptr_t.3: New link to system_data_types(7)
man3/int_fast16_t.3 | 1 + man3/int_fast32_t.3 | 1 + man3/int_fast64_t.3 | 1 + man3/int_fast8_t.3 | 1 + man3/int_fastN_t.3 | 1 + man3/int_least16_t.3 | 1 + man3/int_least32_t.3 | 1 + man3/int_least64_t.3 | 1 + man3/int_least8_t.3 | 1 + man3/int_leastN_t.3 | 1 + man3/intptr_t.3 | 1 + man3/malloc_get_state.3 | 2 +- man3/uint_fast16_t.3 | 1 + man3/uint_fast32_t.3 | 1 + man3/uint_fast64_t.3 | 1 + man3/uint_fast8_t.3 | 1 + man3/uint_fastN_t.3 | 1 + man3/uint_least16_t.3 | 1 + man3/uint_least32_t.3 | 1 + man3/uint_least64_t.3 | 1 + man3/uint_least8_t.3 | 1 + man3/uint_leastN_t.3 | 1 + man3/uintptr_t.3 | 1 + man7/system_data_types.7 | 590 ++++++++++++++++++++++++++++++++++----- 24 files changed, 540 insertions(+), 74 deletions(-) create mode 100644 man3/int_fast16_t.3 create mode 100644 man3/int_fast32_t.3 create mode 100644 man3/int_fast64_t.3 create mode 100644 man3/int_fast8_t.3 create mode 100644 man3/int_fastN_t.3 create mode 100644 man3/int_least16_t.3 create mode 100644 man3/int_least32_t.3 create mode 100644 man3/int_least64_t.3 create mode 100644 man3/int_least8_t.3 create mode 100644 man3/int_leastN_t.3 create mode 100644 man3/intptr_t.3 create mode 100644 man3/uint_fast16_t.3 create mode 100644 man3/uint_fast32_t.3 create mode 100644 man3/uint_fast64_t.3 create mode 100644 man3/uint_fast8_t.3 create mode 100644 man3/uint_fastN_t.3 create mode 100644 man3/uint_least16_t.3 create mode 100644 man3/uint_least32_t.3 create mode 100644 man3/uint_least64_t.3 create mode 100644 man3/uint_least8_t.3 create mode 100644 man3/uint_leastN_t.3 create mode 100644 man3/uintptr_t.3
Signature · 1 line
2.28.0
PATCH 1/16 malloc_get_state.3: ffix
--- man3/malloc_get_state.3 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
man3/malloc_get_state.3 +1 -1
@@ -29,7 +29,7 @@ malloc_get_state, malloc_set_state \- record and restore state of malloc impleme .nf .B #include <malloc.h> .PP -.BI "void* malloc_get_state(void);" +.BI "void *malloc_get_state(void);" .PP .BI "int malloc_set_state(void *" state ); .fi
Signature · 1 line
2.28.0
Michael Kerrisk (man-pages)
AppliedRe: [PATCH 01/16] malloc_get_state.3: ffix
Applied.
Quoted 19 lines · Alejandro Colomar
Signed-off-by Alejandro Colomar <[email protected]>--- man3/malloc_get_state.3 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)man3/malloc_get_state.3 +1
-1@@ -29,7 +29,7 @@ malloc_get_state, malloc_set_state \- record and restore state of malloc impleme .nf .B #include <malloc.h> .PP -.BI "void* malloc_get_state(void);" +.BI "void *malloc_get_state(void);" .PP .BI "int malloc_set_state(void *" state ); .fi
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
PATCH 2/16 system_data_types.7: srcfix
In reply to Alejandro Colomar--- man7/system_data_types.7 | 105 ++++++++++++++++++++++++++------------- 1 file changed, 70 insertions(+), 35 deletions(-)
man7/system_data_types.7 +70 -35
@@ -71,7 +71,8 @@ struct aiocb { For further information about this structure, see .BR aio (7). .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR aio_cancel (3),
@@ -102,7 +103,8 @@ It is the type of the value returned by the .BR div (3) function. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR div (3)
@@ -143,7 +145,8 @@ the type of .I double_t is implementation-defined. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .I float_t
@@ -161,7 +164,8 @@ This type represents the entire floating-point environment, including control modes and status flags; for further details, see .BR fenv (3). .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR fenv (3)
@@ -178,7 +182,8 @@ This type represents the floating-point status flags collectively; for further details see .BR fenv (3). .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR fenv (3)
@@ -195,7 +200,8 @@ Alternatively, .PP An object type used for streams. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR fclose (3),
@@ -243,7 +249,8 @@ the type of .I float_t is implementation-defined. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .I double_t
@@ -270,7 +277,8 @@ A type used to hold group IDs. According to POSIX, this shall be an integer type. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR chown (2),
@@ -299,7 +307,8 @@ this shall be an integer type that can be used to contain a or .IR gid_t . .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR getpriority (2),
@@ -324,7 +333,8 @@ It is the type of the value returned by the .BR imaxdiv (3) function. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR imaxdiv (3)
@@ -379,7 +389,8 @@ is defined and .I long long is less than 128 bits wide. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .I uintmax_t
@@ -453,7 +464,8 @@ for scanning .I int8_t values. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .IR __int128 ,
@@ -505,7 +517,8 @@ Contains members related to the formatting of numeric values. In the "C" locale, its members have the values shown in the comments above. .PP -Conforming to: C11 and later; POSIX.1-2001 and later. +Conforming to: +C11 and later; POSIX.1-2001 and later. .PP See also: .BR setlocale (3),
@@ -532,7 +545,8 @@ It is the type of the value returned by the .BR ldiv (3) function. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR ldiv (3)
@@ -556,7 +570,8 @@ It is the type of the value returned by the .BR lldiv (3) function. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR lldiv (3)
@@ -591,7 +606,8 @@ where the width of is no greater than the width of the type .IR long . .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR fork (2),
@@ -638,7 +654,8 @@ for printing .I ptrdiff_t values. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .I size_t
@@ -666,7 +683,8 @@ typedef struct { .PP This is a structure type used in regular expression matching. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR regexec (3)
@@ -686,9 +704,11 @@ type or a .I ssize_t type. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP -Notes: Prior to POSIX.1-2008, the type was capable of storing +Notes: +Prior to POSIX.1-2008, the type was capable of storing the largest value that can be stored in either an .I off_t type or a
@@ -731,7 +751,8 @@ struct sigevent { For further details about this type, see .BR sigevent (7). .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP Notes: .I <aio.h>
@@ -778,7 +799,8 @@ For further details on this structure (including additional, Linux-specific fields), see .BR sigaction (2). .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR pidfd_send_signal (2),
@@ -802,7 +824,8 @@ or This is a type that represents a set of signals. According to POSIX, this shall be an integer or structure type. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR epoll_pwait (2),
@@ -833,7 +856,8 @@ union sigval { .PP Data passed with a signal. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR pthread_sigqueue (3),
@@ -915,7 +939,8 @@ for printing .I size_t values. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP Notes: .IR <aio.h> ,
@@ -1002,7 +1027,8 @@ by converting the value to and using its length modifier .RB ( j ). .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR read (2),
@@ -1039,7 +1065,8 @@ where the width of is no greater than the width of the type .IR long . .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also the .I timeval
@@ -1068,7 +1095,8 @@ or Used for time in seconds. According to POSIX, it shall be an integer type. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP Notes: .I <sched.h>
@@ -1097,7 +1125,8 @@ Used for timer ID returned by According to POSIX, there are no defined comparison or assignment operators for this type. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR timer_create (2),
@@ -1130,7 +1159,8 @@ struct timespec { .PP Describes times in seconds and nanoseconds. .PP -Conforming to: C11 and later; POSIX.1-2001 and later. +Conforming to: +C11 and later; POSIX.1-2001 and later. .PP See also: .BR clock_gettime (2),
@@ -1161,7 +1191,8 @@ struct timeval { .PP Describes times in seconds and microseconds. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR gettimeofday (2),
@@ -1191,7 +1222,8 @@ A type used to hold user IDs. According to POSIX, this shall be an integer type. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR chown (2),
@@ -1250,7 +1282,8 @@ is defined and .I unsigned long long is less than 128 bits wide. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .I intmax_t
@@ -1327,7 +1360,8 @@ for scanning .I uint16_t values. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .IR __int128 ,
@@ -1361,7 +1395,8 @@ and .BR va_end (3) to traverse the list of arguments. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR va_start (3),
Signature · 1 line
2.28.0
Re: [PATCH 02/16] system_data_types.7: srcfix
Hi Alex,
Quoted 1 line · Alejandro Colomar
Signed-off-by Alejandro Colomar <[email protected]>
I don't mind applying this patch (and I have done so), but I think patches like this need a brief commit message to explain why you are making the change.
Thanks,
Michael
Quoted 353 lines
--- man7/system_data_types.7 | 105 ++++++++++++++++++++++++++------------- 1 file changed, 70 insertions(+), 35 deletions(-)man7/system_data_types.7 +70
-35@@ -71,7 +71,8 @@ struct aiocb { For further information about this structure, see .BR aio (7). .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR aio_cancel (3),@@ -102,7 +103,8 @@ It is the type of the value returned by the .BR div (3) function. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR div (3)@@ -143,7 +145,8 @@ the type of .I double_t is implementation-defined. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .I float_t@@ -161,7 +164,8 @@ This type represents the entire floating-point environment, including control modes and status flags; for further details, see .BR fenv (3). .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR fenv (3)@@ -178,7 +182,8 @@ This type represents the floating-point status flags collectively; for further details see .BR fenv (3). .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR fenv (3)@@ -195,7 +200,8 @@ Alternatively, .PP An object type used for streams. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR fclose (3),@@ -243,7 +249,8 @@ the type of .I float_t is implementation-defined. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .I double_t@@ -270,7 +277,8 @@ A type used to hold group IDs. According to POSIX, this shall be an integer type. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR chown (2),@@ -299,7 +307,8 @@ this shall be an integer type that can be used to contain a or .IR gid_t . .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR getpriority (2),@@ -324,7 +333,8 @@ It is the type of the value returned by the .BR imaxdiv (3) function. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR imaxdiv (3)@@ -379,7 +389,8 @@ is defined and .I long long is less than 128 bits wide. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .I uintmax_t@@ -453,7 +464,8 @@ for scanning .I int8_t values. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .IR __int128 ,@@ -505,7 +517,8 @@ Contains members related to the formatting of numeric values. In the "C" locale, its members have the values shown in the comments above. .PP -Conforming to: C11 and later; POSIX.1-2001 and later. +Conforming to: +C11 and later; POSIX.1-2001 and later. .PP See also: .BR setlocale (3),@@ -532,7 +545,8 @@ It is the type of the value returned by the .BR ldiv (3) function. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR ldiv (3)@@ -556,7 +570,8 @@ It is the type of the value returned by the .BR lldiv (3) function. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR lldiv (3)@@ -591,7 +606,8 @@ where the width of is no greater than the width of the type .IR long . .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR fork (2),@@ -638,7 +654,8 @@ for printing .I ptrdiff_t values. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .I size_t@@ -666,7 +683,8 @@ typedef struct { .PP This is a structure type used in regular expression matching. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR regexec (3)@@ -686,9 +704,11 @@ type or a .I ssize_t type. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP -Notes: Prior to POSIX.1-2008, the type was capable of storing +Notes: +Prior to POSIX.1-2008, the type was capable of storing the largest value that can be stored in either an .I off_t type or a@@ -731,7 +751,8 @@ struct sigevent { For further details about this type, see .BR sigevent (7). .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP Notes: .I <aio.h>@@ -778,7 +799,8 @@ For further details on this structure (including additional, Linux-specific fields), see .BR sigaction (2). .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR pidfd_send_signal (2),@@ -802,7 +824,8 @@ or This is a type that represents a set of signals. According to POSIX, this shall be an integer or structure type. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR epoll_pwait (2),@@ -833,7 +856,8 @@ union sigval { .PP Data passed with a signal. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR pthread_sigqueue (3),@@ -915,7 +939,8 @@ for printing .I size_t values. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP Notes: .IR <aio.h> ,@@ -1002,7 +1027,8 @@ by converting the value to and using its length modifier .RB ( j ). .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR read (2),@@ -1039,7 +1065,8 @@ where the width of is no greater than the width of the type .IR long . .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also the .I timeval@@ -1068,7 +1095,8 @@ or Used for time in seconds. According to POSIX, it shall be an integer type. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP Notes: .I <sched.h>@@ -1097,7 +1125,8 @@ Used for timer ID returned by According to POSIX, there are no defined comparison or assignment operators for this type. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR timer_create (2),@@ -1130,7 +1159,8 @@ struct timespec { .PP Describes times in seconds and nanoseconds. .PP -Conforming to: C11 and later; POSIX.1-2001 and later. +Conforming to: +C11 and later; POSIX.1-2001 and later. .PP See also: .BR clock_gettime (2),@@ -1161,7 +1191,8 @@ struct timeval { .PP Describes times in seconds and microseconds. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR gettimeofday (2),@@ -1191,7 +1222,8 @@ A type used to hold user IDs. According to POSIX, this shall be an integer type. .PP -Conforming to: POSIX.1-2001 and later. +Conforming to: +POSIX.1-2001 and later. .PP See also: .BR chown (2),@@ -1250,7 +1282,8 @@ is defined and .I unsigned long long is less than 128 bits wide. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .I intmax_t@@ -1327,7 +1360,8 @@ for scanning .I uint16_t values. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also the .IR __int128 ,@@ -1361,7 +1395,8 @@ and .BR va_end (3) to traverse the list of arguments. .PP -Conforming to: C99 and later; POSIX.1-2001 and later. +Conforming to: +C99 and later; POSIX.1-2001 and later. .PP See also: .BR va_start (3),
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
PATCH 3/16 system_data_types.7: srcfix
In reply to Alejandro Colomar--- man7/system_data_types.7 | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-)
man7/system_data_types.7 +12 -4
@@ -406,7 +406,10 @@ Include: Alternatively, .IR <inttypes.h> . .PP -.IR int8_t ", " int16_t ", " int32_t ", " int64_t +.IR int8_t , +.IR int16_t , +.IR int32_t , +.I int64_t .PP A signed integer type of a fixed width of exactly N bits,
@@ -418,7 +421,8 @@ capable of storing values in the range substituting N by the appropriate number. .PP According to POSIX, -.IR int8_t ", " int16_t +.IR int8_t , +.IR int16_t and .I int32_t are required;
@@ -1299,7 +1303,10 @@ Include: Alternatively, .IR <inttypes.h> . .PP -.IR uint8_t ", " uint16_t ", " uint32_t ", " uint64_t +.IR uint8_t , +.IR uint16_t , +.IR uint32_t , +.I uint64_t .PP An unsigned integer type of a fixed width of exactly N bits,
@@ -1310,7 +1317,8 @@ capable of storing values in the range [0, substituting N by the appropriate number. .PP According to POSIX, -.IR uint8_t ", " uint16_t +.IR uint8_t , +.IR uint16_t and .I uint32_t are required;
Signature · 1 line
2.28.0
Michael Kerrisk (man-pages)
AppliedRe: [PATCH 03/16] system_data_types.7: srcfix
Hi Alex,
Quoted 4 lines · Alejandro Colomar
Signed-off-by Alejandro Colomar <[email protected]>--- man7/system_data_types.7 | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-)
Yeah, this layout is my preferred form as well.
Applied.
Thanks,
Michael
Quoted 49 lines
man7/system_data_types.7 +12
-4@@ -406,7 +406,10 @@ Include: Alternatively, .IR <inttypes.h> . .PP -.IR int8_t ", " int16_t ", " int32_t ", " int64_t +.IR int8_t , +.IR int16_t , +.IR int32_t , +.I int64_t .PP A signed integer type of a fixed width of exactly N bits,@@ -418,7 +421,8 @@ capable of storing values in the range substituting N by the appropriate number. .PP According to POSIX, -.IR int8_t ", " int16_t +.IR int8_t , +.IR int16_t and .I int32_t are required;@@ -1299,7 +1303,10 @@ Include: Alternatively, .IR <inttypes.h> . .PP -.IR uint8_t ", " uint16_t ", " uint32_t ", " uint64_t +.IR uint8_t , +.IR uint16_t , +.IR uint32_t , +.I uint64_t .PP An unsigned integer type of a fixed width of exactly N bits,@@ -1310,7 +1317,8 @@ capable of storing values in the range [0, substituting N by the appropriate number. .PP According to POSIX, -.IR uint8_t ", " uint16_t +.IR uint8_t , +.IR uint16_t and .I uint32_t are required;
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
PATCH 4/16 system_data_types.7: srcfix
In reply to Alejandro ColomarWe used .br to force a simple line break (with no extra blank line) after the tag.
Recently, we added .RS/.RS, and .RS comes just after the tag, and I realized by accident that .RS already forces a simple line break.
Therefore, .br is completely redundant here, and can be removed.
This way we get rid of "raw" *roff requests in this page.
--- man7/system_data_types.7 | 34 ---------------------------------- 1 file changed, 34 deletions(-)
man7/system_data_types.7 +0 -34
@@ -52,7 +52,6 @@ system_data_types \- overview of system data types .TP .I aiocb .RS -.br Include: .IR <aio.h> . .PP
@@ -88,7 +87,6 @@ See also: .TP .I div_t .RS -.br Include: .IR <stdlib.h> . .PP
@@ -113,7 +111,6 @@ See also: .TP .I double_t .RS -.br Include: .IR <math.h> . .PP
@@ -156,7 +153,6 @@ type in this page. .TP .I fenv_t .RS -.br Include: .IR <fenv.h> . .PP
@@ -174,7 +170,6 @@ See also: .TP .I fexcept_t .RS -.br Include: .IR <fenv.h> . .PP
@@ -192,7 +187,6 @@ See also: .TP .I FILE .RS -.br Include: .IR <stdio.h> . Alternatively,
@@ -217,7 +211,6 @@ See also: .TP .I float_t .RS -.br Include: .IR <math.h> . .PP
@@ -260,7 +253,6 @@ type in this page. .TP .I gid_t .RS -.br Include: .IR <sys/types.h> . Alternatively,
@@ -293,7 +285,6 @@ See also: .TP .I id_t .RS -.br Include: .IR <sys/types.h> . Alternatively,
@@ -318,7 +309,6 @@ See also: .TP .I imaxdiv_t .RS -.br Include: .IR <inttypes.h> . .PP
@@ -343,7 +333,6 @@ See also: .TP .I intmax_t .RS -.br Include: .IR <stdint.h> . Alternatively,
@@ -400,7 +389,6 @@ type in this page. .TP .IR int N _t .RS -.br Include: .IR <stdint.h> . Alternatively,
@@ -484,7 +472,6 @@ types in this page. .TP .I lconv .RS -.br Include: .IR <locale.h> . .PP
@@ -534,7 +521,6 @@ See also: .TP .I ldiv_t .RS -.br Include: .IR <stdlib.h> . .PP
@@ -559,7 +545,6 @@ See also: .TP .I lldiv_t .RS -.br Include: .IR <stdlib.h> . .PP
@@ -584,7 +569,6 @@ See also: .TP .I pid_t .RS -.br Include .IR <sys/types.h> . Alternatively,
@@ -631,7 +615,6 @@ See also: .TP .I ptrdiff_t .RS -.br Include: .IR <stddef.h> . .PP
@@ -671,7 +654,6 @@ types in this page. .TP .I regmatch_t .RS -.br Include: .IR <regex.h> . .PP
@@ -697,7 +679,6 @@ See also: .TP .I regoff_t .RS -.br Include: .IR <regex.h> . .PP
@@ -731,7 +712,6 @@ types in this page. .TP .I sigevent .RS -.br Include: .IR <signal.h> . Alternatively,
@@ -780,7 +760,6 @@ structure in this page. .TP .I siginfo_t .RS -.br Include: .IR <signal.h> . Alternatively,
@@ -817,7 +796,6 @@ See also: .TP .I sigset_t .RS -.br Include: .IR <signal.h> . Alternatively,
@@ -847,7 +825,6 @@ See also: .TP .I sigval .RS -.br Include: .IR <signal.h> . .PP
@@ -880,7 +857,6 @@ in this page. .TP .I size_t .RS -.br Include: .I <stddef.h> or
@@ -981,7 +957,6 @@ types in this page. .TP .I ssize_t .RS -.br Include: .IR <sys/types.h> . Alternatively,
@@ -1052,7 +1027,6 @@ types in this page. .TP .I suseconds_t .RS -.br Include: .IR <sys/types.h> . Alternatively,
@@ -1080,7 +1054,6 @@ structure in this page. .TP .I time_t .RS -.br Include: .I <time.h> or
@@ -1118,7 +1091,6 @@ See also: .TP .I timer_t .RS -.br Include: .IR <sys/types.h> . Alternatively,
@@ -1142,7 +1114,6 @@ See also: .TP .I timespec .RS -.br Include: .IR <time.h> . Alternatively,
@@ -1177,7 +1148,6 @@ See also: .TP .I timeval .RS -.br Include: .IR <sys/time.h> . Alternatively,
@@ -1210,7 +1180,6 @@ See also: .TP .I uid_t .RS -.br Include: .IR <sys/types.h> . Alternatively,
@@ -1241,7 +1210,6 @@ See also: .TP .I uintmax_t .RS -.br Include: .IR <stdint.h> . Alternatively,
@@ -1297,7 +1265,6 @@ type in this page. .TP .IR uint N _t .RS -.br Include: .IR <stdint.h> . Alternatively,
@@ -1384,7 +1351,6 @@ types in this page. .TP .I va_list .RS -.br Include: .IR <stdarg> . Alternatively,
Signature · 1 line
2.28.0
Michael Kerrisk (man-pages)
AppliedRe: [PATCH 04/16] system_data_types.7: srcfix
Hi Alex,
Quoted 11 lines · Alejandro Colomar
We used .br to force a simple line break (with no extra blank line) after the tag.
Recently, we added .RS/.RS, and .RS comes just after the tag, and I realized by accident that .RS already forces a simple line break.
Therefore, .br is completely redundant here, and can be removed.
This way we get rid of "raw" *roff requests in this page.
Signed-off-by Alejandro Colomar <[email protected]>
Great! Thanks for the clean-up.
Applied.
Cheers,
Michael
Quoted 281 lines
--- man7/system_data_types.7 | 34 ---------------------------------- 1 file changed, 34 deletions(-)man7/system_data_types.7 +0
-34@@ -52,7 +52,6 @@ system_data_types \- overview of system data types .TP .I aiocb .RS -.br Include: .IR <aio.h> . .PP@@ -88,7 +87,6 @@ See also: .TP .I div_t .RS -.br Include: .IR <stdlib.h> . .PP@@ -113,7 +111,6 @@ See also: .TP .I double_t .RS -.br Include: .IR <math.h> . .PP@@ -156,7 +153,6 @@ type in this page. .TP .I fenv_t .RS -.br Include: .IR <fenv.h> . .PP@@ -174,7 +170,6 @@ See also: .TP .I fexcept_t .RS -.br Include: .IR <fenv.h> . .PP@@ -192,7 +187,6 @@ See also: .TP .I FILE .RS -.br Include: .IR <stdio.h> . Alternatively,@@ -217,7 +211,6 @@ See also: .TP .I float_t .RS -.br Include: .IR <math.h> . .PP@@ -260,7 +253,6 @@ type in this page. .TP .I gid_t .RS -.br Include: .IR <sys/types.h> . Alternatively,@@ -293,7 +285,6 @@ See also: .TP .I id_t .RS -.br Include: .IR <sys/types.h> . Alternatively,@@ -318,7 +309,6 @@ See also: .TP .I imaxdiv_t .RS -.br Include: .IR <inttypes.h> . .PP@@ -343,7 +333,6 @@ See also: .TP .I intmax_t .RS -.br Include: .IR <stdint.h> . Alternatively,@@ -400,7 +389,6 @@ type in this page. .TP .IR int N _t .RS -.br Include: .IR <stdint.h> . Alternatively,@@ -484,7 +472,6 @@ types in this page. .TP .I lconv .RS -.br Include: .IR <locale.h> . .PP@@ -534,7 +521,6 @@ See also: .TP .I ldiv_t .RS -.br Include: .IR <stdlib.h> . .PP@@ -559,7 +545,6 @@ See also: .TP .I lldiv_t .RS -.br Include: .IR <stdlib.h> . .PP@@ -584,7 +569,6 @@ See also: .TP .I pid_t .RS -.br Include .IR <sys/types.h> . Alternatively,@@ -631,7 +615,6 @@ See also: .TP .I ptrdiff_t .RS -.br Include: .IR <stddef.h> . .PP@@ -671,7 +654,6 @@ types in this page. .TP .I regmatch_t .RS -.br Include: .IR <regex.h> . .PP@@ -697,7 +679,6 @@ See also: .TP .I regoff_t .RS -.br Include: .IR <regex.h> . .PP@@ -731,7 +712,6 @@ types in this page. .TP .I sigevent .RS -.br Include: .IR <signal.h> . Alternatively,@@ -780,7 +760,6 @@ structure in this page. .TP .I siginfo_t .RS -.br Include: .IR <signal.h> . Alternatively,@@ -817,7 +796,6 @@ See also: .TP .I sigset_t .RS -.br Include: .IR <signal.h> . Alternatively,@@ -847,7 +825,6 @@ See also: .TP .I sigval .RS -.br Include: .IR <signal.h> . .PP@@ -880,7 +857,6 @@ in this page. .TP .I size_t .RS -.br Include: .I <stddef.h> or@@ -981,7 +957,6 @@ types in this page. .TP .I ssize_t .RS -.br Include: .IR <sys/types.h> . Alternatively,@@ -1052,7 +1027,6 @@ types in this page. .TP .I suseconds_t .RS -.br Include: .IR <sys/types.h> . Alternatively,@@ -1080,7 +1054,6 @@ structure in this page. .TP .I time_t .RS -.br Include: .I <time.h> or@@ -1118,7 +1091,6 @@ See also: .TP .I timer_t .RS -.br Include: .IR <sys/types.h> . Alternatively,@@ -1142,7 +1114,6 @@ See also: .TP .I timespec .RS -.br Include: .IR <time.h> . Alternatively,@@ -1177,7 +1148,6 @@ See also: .TP .I timeval .RS -.br Include: .IR <sys/time.h> . Alternatively,@@ -1210,7 +1180,6 @@ See also: .TP .I uid_t .RS -.br Include: .IR <sys/types.h> . Alternatively,@@ -1241,7 +1210,6 @@ See also: .TP .I uintmax_t .RS -.br Include: .IR <stdint.h> . Alternatively,@@ -1297,7 +1265,6 @@ type in this page. .TP .IR uint N _t .RS -.br Include: .IR <stdint.h> . Alternatively,@@ -1384,7 +1351,6 @@ types in this page. .TP .I va_list .RS -.br Include: .IR <stdarg> . Alternatively,
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
PATCH 5/16 system_data_types.7: Add int_fastN_t family of types
In reply to Alejandro Colomar--- man7/system_data_types.7 | 76 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+)
man7/system_data_types.7 +76 -0
@@ -329,6 +329,82 @@ C99 and later; POSIX.1-2001 and later. See also: .BR imaxdiv (3) .RE +.\"------------------------------------- int_fastN_t ------------------/ +.TP +.IR int_fast N _t +.RS +Include: +.IR <stdint.h> . +Alternatively, +.IR <inttypes.h> . +.PP +.IR int_fast8_t , +.IR int_fast16_t , +.IR int_fast32_t , +.I int_fast64_t +.PP +The fastest signed integer type +of a width of at least N bits, +N being the value specified in its type name. +According to the C language standard, they shall be +capable of storing values in the range +.RB [ INT_FAST N _MIN , +.BR INT_FAST N _MAX ], +substituting N by the appropriate number. +.PP +The length modifiers for the +.IR int_fast N _t +types for the +.BR printf (3) +family of functions +are expanded by macros of the forms +.BR PRIdFAST N +and +.BR PRIiFAST N +(defined in +.IR <inttypes.h> ); +resulting for example in +.B %"PRIdFAST64" +or +.B %"PRIiFAST64" +for printing +.I int_fast64_t +values. +The length modifiers for the +.IR int_fast N _t +types for the +.BR scanf (3) +family of functions +are expanded by macros of the forms +.BR SCNdFAST N +and +.BR SCNiFAST N, +(defined in +.IR <inttypes.h> ); +resulting for example in +.B %"SCNdFAST8" +or +.B %"SCNiFAST8" +for scanning +.I int_fast8_t +values. +.PP +Conforming to: +C99 and later; POSIX.1-2001 and later. +.PP +Notes: +Some of these types may be optimized for size +instead of raw performance. +.PP +See also the +.IR int_least N _t , +.IR int N _t , +.IR uint_fast N _t , +.IR uint_least N _t +and +.IR uint N _t +types in this page. +.RE .\"------------------------------------- intmax_t ---------------------/ .TP .I intmax_t
Signature · 1 line
2.28.0
Re: [PATCH 05/16] system_data_types.7: Add int_fastN_t family of types
Quoted 70 lines · Alejandro Colomar via Gcc
Signed-off-by Alejandro Colomar <[email protected]>--- man7/system_data_types.7 | 76 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+)man7/system_data_types.7 +56
-0@@ -329,6 +329,82 @@ C99 and later; POSIX.1-2001 and later. See also: .BR imaxdiv (3) .RE +.\"------------------------------------- int_fastN_t ------------------/ +.TP +.IR int_fast N _t +.RS +Include: +.IR <stdint.h> . +Alternatively, +.IR <inttypes.h> . +.PP +.IR int_fast8_t , +.IR int_fast16_t , +.IR int_fast32_t , +.I int_fast64_t +.PP +The fastest signed integer type +of a width of at least N bits, +N being the value specified in its type name. +According to the C language standard, they shall be +capable of storing values in the range +.RB [ INT_FAST N _MIN , +.BR INT_FAST N _MAX ], +substituting N by the appropriate number. +.PP +The length modifiers for the +.IR int_fast N _t +types for the +.BR printf (3) +family of functions +are expanded by macros of the forms +.BR PRIdFAST N +and +.BR PRIiFAST N +(defined in +.IR <inttypes.h> ); +resulting for example in +.B %"PRIdFAST64" +or +.B %"PRIiFAST64" +for printing +.I int_fast64_t +values. +The length modifiers for the +.IR int_fast N _t +types for the +.BR scanf (3) +family of functions +are expanded by macros of the forms +.BR SCNdFAST N +and +.BR SCNiFAST N, +(defined in +.IR <inttypes.h> ); +resulting for example in +.B %"SCNdFAST8" +or +.B %"SCNiFAST8"
man7/system_data_types.7 C99 and later; POSIX.1-2001 and later. · line 397
Quoted 10 lines
man7/system_data_types.7 +10
-0+for scanning +.I int_fast8_t +values. +.PP +Conforming to: +C99 and later; POSIX.1-2001 and later. +.PP +Notes: +Some of these types may be optimized for size +instead of raw performance.
I'm not sure what this tells me as a programmer. What does "raw performance" means exactly? The text above says it's "the fastest", but then it says "may be optimized for size". I don't know how to interpret this. Is it fast or is it small, or something else? Is it optimized for small size? Natural word size? Cacheline size?
I prefer the phrasing of the caveats in the C and POSIX standards which just say it might not be fastest for all purposes.
How about "Where there is no single type that is fastest for all purposes, the implementation may choose any type with the required signedness and at least the minimum width."
I don't see anything in this man page saying that the <stdint.h> types are all typedefs, rather than new types that are distinct from the standard integer types. That seems like useful information.
Re: [PATCH 05/16] system_data_types.7: Add int_fastN_t family of types
On 2020-10-01 13:07, Jonathan Wakely wrote:
[...]
Quoted 13 lines
man7/system_data_types.7 C99 and later; POSIX.1-2001 and later. · line 397
Quoted 3 lines
man7/system_data_types.7 +3
-0+Notes: +Some of these types may be optimized for size +instead of raw performance.I'm not sure what this tells me as a programmer. What does "raw performance" means exactly? The text above says it's "the fastest", but then it says "may be optimized for size". I don't know how to interpret this. Is it fast or is it small, or something else? Is it optimized for small size? Natural word size? Cacheline size?
I prefer the phrasing of the caveats in the C and POSIX standards which just say it might not be fastest for all purposes.
Quoted 8 lines
How about "Where there is no single type that is fastest for all purposes, the implementation may choose any type with the required signedness and at least the minimum width."
I don't see anything in this man page saying that the <
stdint.h> types are all typedefs, rather than new types that are distinct from the standard integer types. That seems like useful information.
Hi Jonathan,
I wasn't sure about how to word it.
In theory, they should be the fastest types; just that.
But then, for some reason, GCC decided thatint_fast8_t should be int8_t instead of int64_t,
because when using arrays of int_fast8_t,
it will create smaller arrays, which will be faster (less cache, etc.).
(I remember having read that a long time ago, but I don't remember the source, or if it's the actual reason).
How would you word that?
Thanks,
Alex
Re: [PATCH 05/16] system_data_types.7: Add int_fastN_t family of types
Quoted 31 lines · Alejandro Colomar
On 2020-10-01 13:07, Jonathan Wakely wrote:
[...]Quoted 13 lines
man7/system_data_types.7 C99 and later; POSIX.1-2001 and later. · line 397
Quoted 3 lines
man7/system_data_types.7 +3
-0+Notes: +Some of these types may be optimized for size +instead of raw performance.I'm not sure what this tells me as a programmer. What does "raw performance" means exactly? The text above says it's "the fastest", but then it says "may be optimized for size". I don't know how to interpret this. Is it fast or is it small, or something else? Is it optimized for small size? Natural word size? Cacheline size?
I prefer the phrasing of the caveats in the C and POSIX standards which just say it might not be fastest for all purposes.
Quoted 8 lines
How about "Where there is no single type that is fastest for all purposes, the implementation may choose any type with the required signedness and at least the minimum width."
I don't see anything in this man page saying that the <
stdint.h> types are all typedefs, rather than new types that are distinct from the standard integer types. That seems like useful information.Hi Jonathan,
I wasn't sure about how to word it.
Quoted 8 lines
In theory, they should be the fastest types; just that.
But then, for some reason, GCC decided thatint_fast8_tshould beint8_tinstead ofint64_t,
because when using arrays ofint_fast8_t,
it will create smaller arrays, which will be faster (less cache, etc.).(I remember having read that a long time ago, but I don't remember the source, or if it's the actual reason).
So then that's still optimized for "raw performance", isn't it? The "raw performance" of copying an array of bytes is better than the "raw performance" of copying an array of 64-bit types. The meaning of "raw performance" depends on what you're doing, so I don't think it's a useful term without context.
Quoted 1 line
How would you word that?
I gave a suggestion above.
Don't use terms like "raw performance" that are meaningless without context. Using "no single type that is fastest for all purposes" makes it clearer that "fastest" isn't something universally true, it might be fastest for some purposes and not others.
Re: [PATCH 05/16] system_data_types.7: Add int_fastN_t family of types
Quoted 3 lines · Jonathan Wakely
Quoted 1 line
How would you word that?
I gave a suggestion above.
Oops, I missed that.
Thanks,
Alex
Re: [PATCH 05/16] system_data_types.7: Add int_fastN_t family of types
In reply to Jonathan WakelyQuoted 5 lines · Jonathan Wakely
I don't see anything in this man page saying that the <
stdint.h> types are all typedefs, rather than new types that are distinct from the standard integer types. That seems like useful information.
Hello Jonathan,
I almost missed this.
We (Michael and I) chose not to give any information
about typedefs in this page.
So the reader should not assume that any type at all, unless explicitly specified, is a typedef.
Any type could be defined however the implementation chooses to do, and this page will only give the requirements for the implementation.
However, if you still think we should be clearer in this point, we might create a NOTE about this in the end of the page.
Your thoughts?
Thanks,
Alex
PATCH 6/16 int_fast8_t.3, int_fast16_t.3, int_fast32_t.3, int_fast64_t.3, int_fastN_t.3: New links to system_data_types(7)
In reply to Alejandro Colomar--- man3/int_fast16_t.3 | 1 + man3/int_fast32_t.3 | 1 + man3/int_fast64_t.3 | 1 + man3/int_fast8_t.3 | 1 + man3/int_fastN_t.3 | 1 + 5 files changed, 5 insertions(+) create mode 100644 man3/int_fast16_t.3 create mode 100644 man3/int_fast32_t.3 create mode 100644 man3/int_fast64_t.3 create mode 100644 man3/int_fast8_t.3 create mode 100644 man3/int_fastN_t.3
man3/int_fast16_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/int_fast32_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/int_fast64_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/int_fast8_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/int_fastN_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
Signature · 1 line
2.28.0
PATCH 7/16 system_data_types.7: Add uint_fastN_t family of types
In reply to Alejandro Colomar--- man7/system_data_types.7 | 79 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 79 insertions(+)
man7/system_data_types.7 +79 -0
@@ -1282,6 +1282,85 @@ See also: .BR getpwnam (2), .BR credentials (7) .RE +.\"------------------------------------- uint_fastN_t -----------------/ +.TP +.IR uint_fast N _t +.RS +Include: +.IR <stdint.h> . +Alternatively, +.IR <inttypes.h> . +.PP +.IR uint_fast8_t , +.IR uint_fast16_t , +.IR uint_fast32_t , +.I uint_fast64_t +.PP +The fastest unsigned integer type +of a width of at least N bits, +N being the value specified in its type name. +According to the C language standard, they shall be +capable of storing values in the range [0, +.BR UINT_FAST N _MAX ], +substituting N by the appropriate number. +.PP +The length modifiers for the +.IR uint_fast N _t +types for the +.BR printf (3) +family of functions +are expanded by macros of the forms +.BR PRIuFAST N, +.BR PRIoFAST N, +.BR PRIxFAST N +and +.BR PRIXFAST N +(defined in +.IR <inttypes.h> ); +resulting for example in +.B %"PRIuFAST32" +or +.B %"PRIxFAST32" +for printing +.I uint_fast32_t +values. +The length modifiers for the +.IR uint_fast N _t +types for the +.BR scanf (3) +family of functions +are expanded by macros of the forms +.BR SCNuFAST N, +.BR SCNoFAST N, +.BR SCNxFAST N +and +.BR SCNXFAST N +(defined in +.IR <inttypes.h> ); +resulting for example in +.B %"SCNuFAST16" +or +.B %"SCNxFAST16" +for scanning +.I uint_fast16_t +values. +.PP +Conforming to: +C99 and later; POSIX.1-2001 and later. +.PP +Notes: +Some of these types may be optimized for size +instead of raw performance. +.PP +See also the +.IR int_fast N _t , +.IR int_least N _t , +.IR int N _t , +.IR uint_least N _t +and +.IR uint N _t +types in this page. +.RE .\"------------------------------------- uintmax_t --------------------/ .TP .I uintmax_t
Signature · 1 line
2.28.0
PATCH 8/16 uint_fast8_t.3, uint_fast16_t.3, uint_fast32_t.3, uint_fast64_t.3, uint_fastN_t.3: New links to system_data_types(7)
In reply to Alejandro Colomar--- man3/uint_fast16_t.3 | 1 + man3/uint_fast32_t.3 | 1 + man3/uint_fast64_t.3 | 1 + man3/uint_fast8_t.3 | 1 + man3/uint_fastN_t.3 | 1 + 5 files changed, 5 insertions(+) create mode 100644 man3/uint_fast16_t.3 create mode 100644 man3/uint_fast32_t.3 create mode 100644 man3/uint_fast64_t.3 create mode 100644 man3/uint_fast8_t.3 create mode 100644 man3/uint_fastN_t.3
man3/uint_fast16_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/uint_fast32_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/uint_fast64_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/uint_fast8_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/uint_fastN_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
Signature · 1 line
2.28.0
PATCH 9/16 system_data_types.7: Add int_leastN_t family of types
In reply to Alejandro Colomar--- man7/system_data_types.7 | 72 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 72 insertions(+)
man7/system_data_types.7 +72 -0
@@ -405,6 +405,78 @@ and .IR uint N _t types in this page. .RE +.\"------------------------------------- int_leastN_t -----------------/ +.TP +.IR int_least N _t +.RS +Include: +.IR <stdint.h> . +Alternatively, +.IR <inttypes.h> . +.PP +.IR int_least8_t , +.IR int_least16_t , +.IR int_least32_t , +.I int_least64_t +.PP +The narrowest signed integer type +of a width of at least N bits, +N being the value specified in its type name. +According to the C language standard, they shall be +capable of storing values in the range +.RB [ INT_LEAST N _MIN , +.BR INT_LEAST N _MAX ], +substituting N by the appropriate number. +.PP +The length modifiers for the +.IR int_least N _t +types for the +.BR printf (3) +family of functions +are expanded by macros of the forms +.BR PRIdLEAST N +and +.BR PRIiLEAST N +(defined in +.IR <inttypes.h> ); +resulting for example in +.B %"PRIdLEAST64" +or +.B %"PRIiLEAST64" +for printing +.I int_least64_t +values. +The length modifiers for the +.IR int_least N _t +types for the +.BR scanf (3) +family of functions +are expanded by macros of the forms +.BR SCNdLEAST N +and +.BR SCNiLEAST N, +(defined in +.IR <inttypes.h> ); +resulting for example in +.B %"SCNdLEAST8" +or +.B %"SCNiLEAST8" +for scanning +.I int_least8_t +values. +.PP +Conforming to: +C99 and later; POSIX.1-2001 and later. +.PP +See also the +.IR int_fast N _t , +.IR int N _t , +.IR uint_fast N _t , +.IR uint_least N _t +and +.IR uint N _t +types in this page. +.RE .\"------------------------------------- intmax_t ---------------------/ .TP .I intmax_t
Signature · 1 line
2.28.0
PATCH 10/16 int_least8_t.3, int_least16_t.3, int_least32_t.3, int_least64_t.3, int_leastN_t.3: New links to system_data_types(7)
In reply to Alejandro Colomar--- man3/int_least16_t.3 | 1 + man3/int_least32_t.3 | 1 + man3/int_least64_t.3 | 1 + man3/int_least8_t.3 | 1 + man3/int_leastN_t.3 | 1 + 5 files changed, 5 insertions(+) create mode 100644 man3/int_least16_t.3 create mode 100644 man3/int_least32_t.3 create mode 100644 man3/int_least64_t.3 create mode 100644 man3/int_least8_t.3 create mode 100644 man3/int_leastN_t.3
man3/int_least16_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/int_least32_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/int_least64_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/int_least8_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/int_leastN_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
Signature · 1 line
2.28.0
PATCH 11/16 system_data_types.7: Add uint_leastN_t family of types
In reply to Alejandro Colomar--- man7/system_data_types.7 | 75 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 75 insertions(+)
man7/system_data_types.7 +75 -0
@@ -1433,6 +1433,81 @@ and .IR uint N _t types in this page. .RE +.\"------------------------------------- uint_leastN_t ----------------/ +.TP +.IR uint_least N _t +.RS +Include: +.IR <stdint.h> . +Alternatively, +.IR <inttypes.h> . +.PP +.IR uint_least8_t , +.IR uint_least16_t , +.IR uint_least32_t , +.I uint_least64_t +.PP +The narrowest unsigned integer type +of a width of at least N bits, +N being the value specified in its type name. +According to the C language standard, they shall be +capable of storing values in the range [0, +.BR UINT_LEAST N _MAX ], +substituting N by the appropriate number. +.PP +The length modifiers for the +.IR uint_least N _t +types for the +.BR printf (3) +family of functions +are expanded by macros of the forms +.BR PRIuLEST N, +.BR PRIoLEAST N, +.BR PRIxLEAST N +and +.BR PRIXLEAST N +(defined in +.IR <inttypes.h> ); +resulting for example in +.B %"PRIuLEAST32" +or +.B %"PRIxLEAST32" +for printing +.I uint_least32_t +values. +The length modifiers for the +.IR uint_least N _t +types for the +.BR scanf (3) +family of functions +are expanded by macros of the forms +.BR SCNuLEAST N, +.BR SCNoLEAST N, +.BR SCNxLEAST N +and +.BR SCNXLEAST N +(defined in +.IR <inttypes.h> ); +resulting for example in +.B %"SCNuLEAST16" +or +.B %"SCNxLEAST16" +for scanning +.I uint_least16_t +values. +.PP +Conforming to: +C99 and later; POSIX.1-2001 and later. +.PP +See also the +.IR int_fast N _t , +.IR int_least N _t , +.IR int N _t , +.IR uint_fast N _t +and +.IR uint N _t +types in this page. +.RE .\"------------------------------------- uintmax_t --------------------/ .TP .I uintmax_t
Signature · 1 line
2.28.0
PATCH 12/16 uint_least8_t.3, uint_least16_t.3, uint_least32_t.3, uint_least64_t.3, uint_leastN_t.3: New links to system_data_types(7)
In reply to Alejandro Colomar--- man3/uint_least16_t.3 | 1 + man3/uint_least32_t.3 | 1 + man3/uint_least64_t.3 | 1 + man3/uint_least8_t.3 | 1 + man3/uint_leastN_t.3 | 1 + 5 files changed, 5 insertions(+) create mode 100644 man3/uint_least16_t.3 create mode 100644 man3/uint_least32_t.3 create mode 100644 man3/uint_least64_t.3 create mode 100644 man3/uint_least8_t.3 create mode 100644 man3/uint_leastN_t.3
man3/uint_least16_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/uint_least32_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/uint_least64_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/uint_least8_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
man3/uint_leastN_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
Signature · 1 line
2.28.0
PATCH 13/16 system_data_types.7: Add 'intptr_t'
In reply to Alejandro Colomar--- man7/system_data_types.7 | 65 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+)
man7/system_data_types.7 +65 -0
@@ -616,6 +616,71 @@ and .I unsigned __int128 types in this page. .RE +.\"------------------------------------- intptr_t ---------------------/ +.TP +.I intptr_t +.RS +Include: +.IR <stdint.h> . +Alternatively, +.IR <inttypes.h> . +.PP +A signed integer type +such that any valid +.RI ( "void *" ) +value can be converted to this type and back. +According to the C language standard, it shall be +capable of storing values in the range +.RB [ INTPTR_MIN , +.BR INTPTR_MAX ]. +.PP +The length modifier for +.I intptr_t +for the +.BR printf (3) +family of functions +is expanded by the macros +.B PRIdPTR +and +.B PRIiPTR +(defined in +.IR <inttypes.h> ); +resulting commonly in +.B %"PRIdPTR" +or +.B %"PRIiPTR" +for printing +.I intptr_t +values. +The length modifier for +.I intptr_t +for the +.BR scanf (3) +family of functions +is expanded by the macros +.B SCNdPTR +and +.B SCNiPTR, +(defined in +.IR <inttypes.h> ); +resulting commonly in +.B %"SCNdPTR" +or +.B %"SCNiPTR" +for scanning +.I intptr_t +values. +.PP +Conforming to: +C99 and later; POSIX.1-2001 and later. +.PP +See also the +.I uintptr_t +and +.I void * +.\" TODO: Document void * +types in this page. +.RE .\"------------------------------------- lconv ------------------------/ .TP .I lconv
Signature · 1 line
2.28.0
Re: [PATCH 13/16] system_data_types.7: Add 'intptr_t'
Hi Alex,
Quoted 4 lines · Alejandro Colomar
Signed-off-by Alejandro Colomar <[email protected]>--- man7/system_data_types.7 | 65 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+)
Thanks. Patch applied.
Cheers,
Michael
Quoted 77 lines
man7/system_data_types.7 +65
-0@@ -616,6 +616,71 @@ and .I unsigned __int128 types in this page. .RE +.\"------------------------------------- intptr_t ---------------------/ +.TP +.I intptr_t +.RS +Include: +.IR <stdint.h> . +Alternatively, +.IR <inttypes.h> . +.PP +A signed integer type +such that any valid +.RI ( "void *" ) +value can be converted to this type and back. +According to the C language standard, it shall be +capable of storing values in the range +.RB [ INTPTR_MIN , +.BR INTPTR_MAX ]. +.PP +The length modifier for +.I intptr_t +for the +.BR printf (3) +family of functions +is expanded by the macros +.B PRIdPTR +and +.B PRIiPTR +(defined in +.IR <inttypes.h> ); +resulting commonly in +.B %"PRIdPTR" +or +.B %"PRIiPTR" +for printing +.I intptr_t +values. +The length modifier for +.I intptr_t +for the +.BR scanf (3) +family of functions +is expanded by the macros +.B SCNdPTR +and +.B SCNiPTR, +(defined in +.IR <inttypes.h> ); +resulting commonly in +.B %"SCNdPTR" +or +.B %"SCNiPTR" +for scanning +.I intptr_t +values. +.PP +Conforming to: +C99 and later; POSIX.1-2001 and later. +.PP +See also the +.I uintptr_t +and +.I void * +.\" TODO: Document void * +types in this page. +.RE .\"------------------------------------- lconv ------------------------/ .TP .I lconv
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
PATCH 14/16 intptr_t.3: New link to system_data_types(7)
In reply to Alejandro Colomar--- man3/intptr_t.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/intptr_t.3
man3/intptr_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
Signature · 1 line
2.28.0
Michael Kerrisk (man-pages)
AppliedRe: [PATCH 14/16] intptr_t.3: New link to system_data_types(7)
Applied.
Quoted 14 lines · Alejandro Colomar
Signed-off-by Alejandro Colomar <[email protected]>--- man3/intptr_t.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/intptr_t.3man3/intptr_t.3 new file +1
-0@@ -0,0 +1 @@ +.so man7/system_data_types.7
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
PATCH 15/16 system_data_types.7: Add 'uintptr_t'
In reply to Alejandro Colomar--- man7/system_data_types.7 | 68 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+)
man7/system_data_types.7 +68 -0
@@ -1714,6 +1714,74 @@ and .I unsigned __int128 types in this page. .RE +.\"------------------------------------- uintptr_t --------------------/ +.TP +.I uintptr_t +.RS +Include: +.IR <stdint.h> . +Alternatively, +.IR <inttypes.h> . +.PP +An unsigned integer type +such that any valid +.RI ( "void *" ) +value can be converted to this type and back. +According to the C language standard, it shall be +capable of storing values in the range [0, +.BR UINTPTR_MAX ]. +.PP +The length modifier for +.I uintptr_t +for the +.BR printf (3) +family of functions +is expanded by the macros +.BR PRIuPTR, +.BR PRIoPTR, +.B PRIxPTR +and +.B PRIXPTR +(defined in +.IR <inttypes.h> ); +resulting commonly in +.B %"PRIuPTR" +or +.B %"PRIxPTR" +for printing +.I uintptr_t +values. +The length modifier for +.I uintptr_t +for the +.BR scanf (3) +family of functions +is expanded by the macros +.BR SCNuPTR, +.BR SCNoPTR, +.B SCNxPTR +and +.B SCNXPTR +(defined in +.IR <inttypes.h> ); +resulting commonly in +.B %"SCNuPTR" +or +.B %"SCNxPTR" +for scanning +.I uintptr_t +values. +.PP +Conforming to: +C99 and later; POSIX.1-2001 and later. +.PP +See also the +.I intptr_t +and +.I void * +.\" TODO: Document void * +types in this page. +.RE .\"------------------------------------- va_list ----------------------/ .TP .I va_list
Signature · 1 line
2.28.0
Re: [PATCH 15/16] system_data_types.7: Add 'uintptr_t'
Hi ALex,
Quoted 4 lines · Alejandro Colomar
Signed-off-by Alejandro Colomar <[email protected]>--- man7/system_data_types.7 | 68 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+)
Thanks. Patch applied.
Cheers,
Michael
Quoted 80 lines
man7/system_data_types.7 +68
-0@@ -1714,6 +1714,74 @@ and .I unsigned __int128 types in this page. .RE +.\"------------------------------------- uintptr_t --------------------/ +.TP +.I uintptr_t +.RS +Include: +.IR <stdint.h> . +Alternatively, +.IR <inttypes.h> . +.PP +An unsigned integer type +such that any valid +.RI ( "void *" ) +value can be converted to this type and back. +According to the C language standard, it shall be +capable of storing values in the range [0, +.BR UINTPTR_MAX ]. +.PP +The length modifier for +.I uintptr_t +for the +.BR printf (3) +family of functions +is expanded by the macros +.BR PRIuPTR, +.BR PRIoPTR, +.B PRIxPTR +and +.B PRIXPTR +(defined in +.IR <inttypes.h> ); +resulting commonly in +.B %"PRIuPTR" +or +.B %"PRIxPTR" +for printing +.I uintptr_t +values. +The length modifier for +.I uintptr_t +for the +.BR scanf (3) +family of functions +is expanded by the macros +.BR SCNuPTR, +.BR SCNoPTR, +.B SCNxPTR +and +.B SCNXPTR +(defined in +.IR <inttypes.h> ); +resulting commonly in +.B %"SCNuPTR" +or +.B %"SCNxPTR" +for scanning +.I uintptr_t +values. +.PP +Conforming to: +C99 and later; POSIX.1-2001 and later. +.PP +See also the +.I intptr_t +and +.I void * +.\" TODO: Document void * +types in this page. +.RE .\"------------------------------------- va_list ----------------------/ .TP .I va_list
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
PATCH 16/16 uintptr_t.3: New link to system_data_types(7)
In reply to Alejandro Colomar--- man3/uintptr_t.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/uintptr_t.3
man3/uintptr_t.3 new file +1 -0
@@ -0,0 +1 @@ +.so man7/system_data_types.7
Signature · 1 line
2.28.0
Michael Kerrisk (man-pages)
AppliedRe: [PATCH 16/16] uintptr_t.3: New link to system_data_types(7)
Applied.
Quoted 14 lines · Alejandro Colomar
Signed-off-by Alejandro Colomar <[email protected]>--- man3/uintptr_t.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/uintptr_t.3man3/uintptr_t.3 new file +1
-0@@ -0,0 +1 @@ +.so man7/system_data_types.7
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
Hi Alex,
Quoted 4 lines · Alejandro Colomar
Hi Michael,
Here are a few fixes (including one removing .br), and then the remaining stdint types.
These very long patch series are a bit overwhelming for me. I'd have preferred a few smaller patch series. For example, I think I would have preferred 3 series like this:
1-4
5-12
13-16
One reason is that the multiple parallel reply threads that sometimes occur can sometimes be rather difficult to track. (Your patches have started some quite useful conversations!)
For example, I suspect Jonathan's comments may trigger changes for patches 5-12.
For now, I'm applying 1-4 and 13-16. It looks like some reworking is going to be needed for the others. When you do resubmit them, please start a new thread (rather than replying into this thread).
Thanks,
Michael
Quoted 61 lines
Alejandro Colomar (16):
malloc_get_state.3: ffix
system_data_types.7: srcfix
system_data_types.7: srcfix
system_data_types.7: srcfix
system_data_types.7: Addint_fastN_tfamily of types int_fast8_t.3, int_fast16_t.3, int_fast32_t.3, int_fast64_t.3,
int_fastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Adduint_fastN_tfamily of types uint_fast8_t.3, uint_fast16_t.3, uint_fast32_t.3, uint_fast64_t.3,
uint_fastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Addint_leastN_tfamily of types int_least8_t.3, int_least16_t.3, int_least32_t.3, int_least64_t.3,
int_leastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Adduint_leastN_tfamily of types uint_least8_t.3, uint_least16_t.3, uint_least32_t.3, uint_least64_t.3,
uint_leastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Add 'intptr_t'
intptr_t.3: New link tosystem_data_types(7)system_data_types.7: Add 'uintptr_t'
uintptr_t.3: New link tosystem_data_types(7)man3/int_fast16_t.3 | 1 + man3/int_fast32_t.3 | 1 + man3/int_fast64_t.3 | 1 + man3/int_fast8_t.3 | 1 + man3/int_fastN_t.3 | 1 + man3/int_least16_t.3 | 1 + man3/int_least32_t.3 | 1 + man3/int_least64_t.3 | 1 + man3/int_least8_t.3 | 1 + man3/int_leastN_t.3 | 1 + man3/intptr_t.3 | 1 + man3/malloc_get_state.3 | 2 +- man3/uint_fast16_t.3 | 1 + man3/uint_fast32_t.3 | 1 + man3/uint_fast64_t.3 | 1 + man3/uint_fast8_t.3 | 1 + man3/uint_fastN_t.3 | 1 + man3/uint_least16_t.3 | 1 + man3/uint_least32_t.3 | 1 + man3/uint_least64_t.3 | 1 + man3/uint_least8_t.3 | 1 + man3/uint_leastN_t.3 | 1 + man3/uintptr_t.3 | 1 + man7/system_data_types.7 | 590 ++++++++++++++++++++++++++++++++++----- 24 files changed, 540 insertions(+), 74 deletions(-) create mode 100644 man3/int_fast16_t.3 create mode 100644 man3/int_fast32_t.3 create mode 100644 man3/int_fast64_t.3 create mode 100644 man3/int_fast8_t.3 create mode 100644 man3/int_fastN_t.3 create mode 100644 man3/int_least16_t.3 create mode 100644 man3/int_least32_t.3 create mode 100644 man3/int_least64_t.3 create mode 100644 man3/int_least8_t.3 create mode 100644 man3/int_leastN_t.3 create mode 100644 man3/intptr_t.3 create mode 100644 man3/uint_fast16_t.3 create mode 100644 man3/uint_fast32_t.3 create mode 100644 man3/uint_fast64_t.3
Quoted 9 lines
create mode 100644 man3/uint_fast8_t.3 create mode 100644 man3/uint_fastN_t.3 create mode 100644 man3/uint_least16_t.3 create mode 100644 man3/uint_least32_t.3 create mode 100644 man3/uint_least64_t.3 create mode 100644 man3/uint_least8_t.3 create mode 100644 man3/uint_leastN_t.3 create mode 100644 man3/uintptr_t.3
H
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
Hi Michael,
I did it this way because then you have a clearly ordered list of the commits, and in which order they go,
so I thought it might be easier for you (creating less conflicts).
And also, I can hold any more recent patches, such as __int128, for when you finish applying the previous set, so I fix the conflicts before you ever see them.
Don't you think?
I don't mind fixing for example patch 5,
and then rebasing the rest (and also the patches I didn't send yet), and resending them as an answer to v1 00/16.
But if you still prefer smaller sets, I'll send you smaller sets.
It's just that these patches are usually very dependent of the previous ones, and therefore prone to conflicts if you don't apply them in the same exact order.
Your thoughts?
Thanks,
Alex
Quoted 103 lines · Michael Kerrisk (man-pages)
Hi Alex,
Quoted 4 lines · Alejandro Colomar
Hi Michael,
Here are a few fixes (including one removing .br), and then the remaining stdint types.
These very long patch series are a bit overwhelming for me. I'd have preferred a few smaller patch series. For example, I think I would have preferred 3 series like this:
1-4
5-12
13-16One reason is that the multiple parallel reply threads that sometimes occur can sometimes be rather difficult to track. (Your patches have started some quite useful conversations!)
For example, I suspect Jonathan's comments may trigger changes for patches 5-12.
For now, I'm applying 1-4 and 13-16. It looks like some reworking is going to be needed for the others. When you do resubmit them, please start a new thread (rather than replying into this thread).
Thanks,
Michael
Quoted 61 lines
Alejandro Colomar (16):
malloc_get_state.3: ffix
system_data_types.7: srcfix
system_data_types.7: srcfix
system_data_types.7: srcfix
system_data_types.7: Addint_fastN_tfamily of types int_fast8_t.3, int_fast16_t.3, int_fast32_t.3, int_fast64_t.3,
int_fastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Adduint_fastN_tfamily of types uint_fast8_t.3, uint_fast16_t.3, uint_fast32_t.3, uint_fast64_t.3,
uint_fastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Addint_leastN_tfamily of types int_least8_t.3, int_least16_t.3, int_least32_t.3, int_least64_t.3,
int_leastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Adduint_leastN_tfamily of types uint_least8_t.3, uint_least16_t.3, uint_least32_t.3, uint_least64_t.3,
uint_leastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Add 'intptr_t'
intptr_t.3: New link tosystem_data_types(7)system_data_types.7: Add 'uintptr_t'
uintptr_t.3: New link tosystem_data_types(7)man3/int_fast16_t.3 | 1 + man3/int_fast32_t.3 | 1 + man3/int_fast64_t.3 | 1 + man3/int_fast8_t.3 | 1 + man3/int_fastN_t.3 | 1 + man3/int_least16_t.3 | 1 + man3/int_least32_t.3 | 1 + man3/int_least64_t.3 | 1 + man3/int_least8_t.3 | 1 + man3/int_leastN_t.3 | 1 + man3/intptr_t.3 | 1 + man3/malloc_get_state.3 | 2 +- man3/uint_fast16_t.3 | 1 + man3/uint_fast32_t.3 | 1 + man3/uint_fast64_t.3 | 1 + man3/uint_fast8_t.3 | 1 + man3/uint_fastN_t.3 | 1 + man3/uint_least16_t.3 | 1 + man3/uint_least32_t.3 | 1 + man3/uint_least64_t.3 | 1 + man3/uint_least8_t.3 | 1 + man3/uint_leastN_t.3 | 1 + man3/uintptr_t.3 | 1 + man7/system_data_types.7 | 590 ++++++++++++++++++++++++++++++++++----- 24 files changed, 540 insertions(+), 74 deletions(-)create mode 100644 man3/int_fast16_t.3
create mode 100644 man3/int_fast32_t.3
create mode 100644 man3/int_fast64_t.3
create mode 100644 man3/int_fast8_t.3
create mode 100644 man3/int_fastN_t.3
create mode 100644 man3/int_least16_t.3
create mode 100644 man3/int_least32_t.3
create mode 100644 man3/int_least64_t.3
create mode 100644 man3/int_least8_t.3
create mode 100644 man3/int_leastN_t.3
create mode 100644 man3/intptr_t.3
create mode 100644 man3/uint_fast16_t.3
create mode 100644 man3/uint_fast32_t.3
create mode 100644 man3/uint_fast64_t.3Quoted 9 lines
create mode 100644 man3/uint_fast8_t.3
create mode 100644 man3/uint_fastN_t.3
create mode 100644 man3/uint_least16_t.3
create mode 100644 man3/uint_least32_t.3
create mode 100644 man3/uint_least64_t.3
create mode 100644 man3/uint_least8_t.3
create mode 100644 man3/uint_leastN_t.3
create mode 100644 man3/uintptr_t.3H
Hi Alex,
Quoted 5 lines · Alejandro Colomar
Hi Michael,
I did it this way because then you have a clearly ordered list of the commits, and in which order they go,
so I thought it might be easier for you (creating less conflicts).
Yes, I understand the rationale. But when I get a series of loosely related patches in a series of 20, and multiple conversations start about independent topics, I'm finding it quite some effort to keep track.
Quoted 11 lines
And also, I can hold any more recent patches, such as
__int128, for when you finish applying the previous set, so I fix the conflicts before you ever see them.Don't you think?
I don't mind fixing for example patch 5,
and then rebasing the rest (and also the patches I didn't send yet), and resending them as an answer to v1 00/16.But if you still prefer smaller sets, I'll send you smaller sets.
I do prefer smaller sets. And yes, occasionally things may go wrong in terms of patch conflicts, but I think that may be a smaller than the problem I note above.
Quoted 5 lines
It's just that these patches are usually very dependent of the previous ones, and therefore prone to conflicts if you don't apply them in the same exact order.
Your thoughts?
As you can see, there's no perfect solution here. In such situations what I try to do (where possible) is order the patches from least contentious to most contentious. That way, the patches that are almost certainly going to be applied are loaded at the front and the chance of having to rebasing later patches in a series is lower.
Thanks,
Michael
Quoted 104 lines · Michael Kerrisk (man-pages)
Quoted 103 lines
Hi Alex,
Quoted 4 lines · Alejandro Colomar
Hi Michael,
Here are a few fixes (including one removing .br), and then the remaining stdint types.
These very long patch series are a bit overwhelming for me. I'd have preferred a few smaller patch series. For example, I think I would have preferred 3 series like this:
1-4
5-12
13-16One reason is that the multiple parallel reply threads that sometimes occur can sometimes be rather difficult to track. (Your patches have started some quite useful conversations!)
For example, I suspect Jonathan's comments may trigger changes for patches 5-12.
For now, I'm applying 1-4 and 13-16. It looks like some reworking is going to be needed for the others. When you do resubmit them, please start a new thread (rather than replying into this thread).
Thanks,
Michael
Quoted 61 lines
Alejandro Colomar (16):
malloc_get_state.3: ffix
system_data_types.7: srcfix
system_data_types.7: srcfix
system_data_types.7: srcfix
system_data_types.7: Addint_fastN_tfamily of types int_fast8_t.3, int_fast16_t.3, int_fast32_t.3, int_fast64_t.3,
int_fastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Adduint_fastN_tfamily of types uint_fast8_t.3, uint_fast16_t.3, uint_fast32_t.3, uint_fast64_t.3,
uint_fastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Addint_leastN_tfamily of types int_least8_t.3, int_least16_t.3, int_least32_t.3, int_least64_t.3,
int_leastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Adduint_leastN_tfamily of types uint_least8_t.3, uint_least16_t.3, uint_least32_t.3, uint_least64_t.3,
uint_leastN_t.3: New links tosystem_data_types(7)
system_data_types.7: Add 'intptr_t'
intptr_t.3: New link tosystem_data_types(7)system_data_types.7: Add 'uintptr_t'
uintptr_t.3: New link tosystem_data_types(7)man3/int_fast16_t.3 | 1 + man3/int_fast32_t.3 | 1 + man3/int_fast64_t.3 | 1 + man3/int_fast8_t.3 | 1 + man3/int_fastN_t.3 | 1 + man3/int_least16_t.3 | 1 + man3/int_least32_t.3 | 1 + man3/int_least64_t.3 | 1 + man3/int_least8_t.3 | 1 + man3/int_leastN_t.3 | 1 + man3/intptr_t.3 | 1 + man3/malloc_get_state.3 | 2 +- man3/uint_fast16_t.3 | 1 + man3/uint_fast32_t.3 | 1 + man3/uint_fast64_t.3 | 1 + man3/uint_fast8_t.3 | 1 + man3/uint_fastN_t.3 | 1 + man3/uint_least16_t.3 | 1 + man3/uint_least32_t.3 | 1 + man3/uint_least64_t.3 | 1 + man3/uint_least8_t.3 | 1 + man3/uint_leastN_t.3 | 1 + man3/uintptr_t.3 | 1 + man7/system_data_types.7 | 590 ++++++++++++++++++++++++++++++++++----- 24 files changed, 540 insertions(+), 74 deletions(-)create mode 100644 man3/int_fast16_t.3
create mode 100644 man3/int_fast32_t.3
create mode 100644 man3/int_fast64_t.3
create mode 100644 man3/int_fast8_t.3
create mode 100644 man3/int_fastN_t.3
create mode 100644 man3/int_least16_t.3
create mode 100644 man3/int_least32_t.3
create mode 100644 man3/int_least64_t.3
create mode 100644 man3/int_least8_t.3
create mode 100644 man3/int_leastN_t.3
create mode 100644 man3/intptr_t.3
create mode 100644 man3/uint_fast16_t.3
create mode 100644 man3/uint_fast32_t.3
create mode 100644 man3/uint_fast64_t.3Quoted 9 lines
create mode 100644 man3/uint_fast8_t.3
create mode 100644 man3/uint_fastN_t.3
create mode 100644 man3/uint_least16_t.3
create mode 100644 man3/uint_least32_t.3
create mode 100644 man3/uint_least64_t.3
create mode 100644 man3/uint_least8_t.3
create mode 100644 man3/uint_leastN_t.3
create mode 100644 man3/uintptr_t.3H
Signature · 3 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
Okay then :)
Thanks,
Alex
Quoted 80 lines · Michael Kerrisk (man-pages)
Hi Alex,
Quoted 5 lines · Alejandro Colomar
Hi Michael,
I did it this way because then you have a clearly ordered list of the commits, and in which order they go,
so I thought it might be easier for you (creating less conflicts).Yes, I understand the rationale. But when I get a series of loosely related patches in a series of 20, and multiple conversations start about independent topics, I'm finding it quite some effort to keep track.
Quoted 11 lines
And also, I can hold any more recent patches, such as
__int128, for when you finish applying the previous set, so I fix the conflicts before you ever see them.Don't you think?
I don't mind fixing for example patch 5,
and then rebasing the rest (and also the patches I didn't send yet), and resending them as an answer to v1 00/16.But if you still prefer smaller sets, I'll send you smaller sets.
I do prefer smaller sets. And yes, occasionally things may go wrong in terms of patch conflicts, but I think that may be a smaller than the problem I note above.
Quoted 5 lines
It's just that these patches are usually very dependent of the previous ones, and therefore prone to conflicts if you don't apply them in the same exact order.
Your thoughts?
As you can see, there's no perfect solution here. In such situations what I try to do (where possible) is order the patches from least contentious to most contentious. That way, the patches that are almost certainly going to be applied are loaded at the front and the chance of having to rebasing later patches in a series is lower.
Thanks,
Michael
Quoted 31 lines · Michael Kerrisk (man-pages)
Quoted 30 lines
Hi Alex,
Quoted 4 lines · Alejandro Colomar
Hi Michael,
Here are a few fixes (including one removing .br), and then the remaining stdint types.
These very long patch series are a bit overwhelming for me. I'd have preferred a few smaller patch series. For example, I think I would have preferred 3 series like this:
1-4
5-12
13-16One reason is that the multiple parallel reply threads that sometimes occur can sometimes be rather difficult to track. (Your patches have started some quite useful conversations!)
For example, I suspect Jonathan's comments may trigger changes for patches 5-12.
For now, I'm applying 1-4 and 13-16. It looks like some reworking is going to be needed for the others. When you do resubmit them, please start a new thread (rather than replying into this thread).
Thanks,
Michael