Re: [PATCH v8] C, ObjC: Add -Wunterminated-string-initialization

Ping. I see that GCC-14 has been released recently. This is a gentle ping to see if this is a better time for this patch. Have a lovely day! Alex signature.asc Description: PGP signature

[PATCH v8] C, ObjC: Add -Wunterminated-string-initialization

ski Cc: Jonathan Wakely Cc: Andrew Clayton Cc: Martin Uecker Cc: David Malcolm Cc: Mike Stump Cc: Joseph Myers Signed-off-by: Alejandro Colomar --- Hi! I've added a changelog to the commit message, as requested by Sandra, and noted her review. Have a lovely day! Alex Range-diff against

[PATCH v7] C, ObjC: Add -Wunterminated-string-initialization

quot;G. Branden Robinson" Cc: Ralph Corderoy Cc: Dave Kemper Cc: Larry McVoy Cc: Andrew Pinski Cc: Jonathan Wakely Cc: Andrew Clayton Cc: Martin Uecker Cc: David Malcolm Cc: Mike Stump Cc: Joseph Myers Cc: Sandra Loosemore Signed-off-by: Alejandro Colomar --- Range-diff against v6: 1:

Re: [PATCH v6] C, ObjC: Add -Wunterminated-string-initialization

On Tue, Mar 05, 2024 at 09:20:42PM +0100, Alejandro Colomar wrote: > Hi! > > v6: > - Small wording fix in c.opt > - Document the option in invoke.texi > > I tried again, but didn't find much alphabetic order in there, so put > it where Mike suggested, after -Wa

[PATCH v6] C, ObjC: Add -Wunterminated-string-initialization

quot;G. Branden Robinson" Cc: Ralph Corderoy Cc: Dave Kemper Cc: Larry McVoy Cc: Andrew Pinski Cc: Jonathan Wakely Cc: Andrew Clayton Cc: Martin Uecker Cc: David Malcolm Cc: Mike Stump Cc: Joseph Myers Cc: Sandra Loosemore Signed-off-by: Alejandro Colomar --- Hi! v6: - Small wo

Re: [PATCH v5 RESEND] C, ObjC: Add -Wunterminated-string-initialization

Hi Joseph, On Mon, Feb 26, 2024 at 03:24:32PM +, Joseph Myers wrote: > On Sun, 25 Feb 2024, Mike Stump wrote: > > > On Feb 6, 2024, at 2:45 AM, Alejandro Colomar wrote: > > > > > > Warn about the following: > > > > > >char s[3] =

Re: [PATCH v5 RESEND] C, ObjC: Add -Wunterminated-string-initialization

Hi Mike, Joseph, On Sun, Feb 25, 2024 at 10:10:09AM -0800, Mike Stump wrote: > On Feb 6, 2024, at 2:45 AM, Alejandro Colomar wrote: > > > > Warn about the following: > > > >char s[3] = "foo"; > > No ObjC specific impact here, so no need for

[PATCH v5 RESEND] C, ObjC: Add -Wunterminated-string-initialization

quot;G. Branden Robinson" Cc: Ralph Corderoy Cc: Dave Kemper Cc: Larry McVoy Cc: Andrew Pinski Cc: Jonathan Wakely Cc: Andrew Clayton Cc: Martin Uecker Cc: David Malcolm Signed-off-by: Alejandro Colomar --- v5: - Fix existing C++-compat tests. [reported by ] gcc/c-family/c.

Re: [PATCH v5] C, ObjC: Add -Wunterminated-string-initialization

Hi, Gentle ping, just again a little before v14 stage 3. Do I need to do anything else with this patch? The CI seemed to say it's ok. Cheers, Alex On Sun, Oct 01, 2023 at 06:24:00PM +0200, Alejandro Colomar wrote: > Warn about the following: > > char s[3] = "foo"

Ping: [PATCH v5] C, ObjC: Add -Wunterminated-string-initialization

Hi, Gentle ping here. Thanks, Alex On Sun, Oct 01, 2023 at 06:24:00PM +0200, Alejandro Colomar wrote: > Warn about the following: > > char s[3] = "foo"; > > Initializing a char array with a string literal of the same length as > the size of the array i

[PATCH v5] C, ObjC: Add -Wunterminated-string-initialization

quot;G. Branden Robinson" Cc: Ralph Corderoy Cc: Dave Kemper Cc: Larry McVoy Cc: Andrew Pinski Cc: Jonathan Wakely Cc: Andrew Clayton Cc: Martin Uecker Cc: David Malcolm Signed-off-by: Alejandro Colomar --- v5: - Fix existing C++-compat tests. [reported by ] gcc/c-family/c.

[PATCH v4] C, ObjC: Add -Wunterminated-string-initialization

rg/archive/html/groff/2022-11/msg00063.html> Link: <https://inbox.sourceware.org/gcc/36da94eb-1cac-5ae8-7fea-ec66160cf...@gmail.com/T/> Acked-by: Doug McIlroy Cc: "G. Branden Robinson" Cc: Ralph Corderoy Cc: Dave Kemper Cc: Larry McVoy Cc: Andrew Pinski Cc: Jonathan Wakely

[PATCH v3] C, ObjC: Add -Wunterminated-string-initialization

From: Alejandro Colomar Warn about the following: char s[3] = "foo"; Initializing a char array with a string literal of the same length as the size of the array is usually a mistake. Rarely is the case where one wants to create a non-terminated character sequence from a stri

Re: [PATCH v2] C, ObjC: Add -Wunterminated-string-initialization

On Sun, Oct 01, 2023 at 09:37:59AM +0200, Martin Uecker wrote: > > (I shortened the recipient list) > > Am Sonntag, dem 01.10.2023 um 02:55 +0200 schrieb Alejandro Colomar: > > > > > ... > > I ran the tests, and get some unexpected failure. I used dg-warni

Re: [PATCH v2] C, ObjC: Add -Wunterminated-string-initialization

Hi David, Sorry for the half-year delay! I have some update. :) On Fri, Mar 24, 2023 at 10:53:22AM -0400, David Malcolm wrote: > On Fri, 2023-03-24 at 14:39 +0100, Alejandro Colomar via Gcc-patches > wrote: > > Warn about the following: > > > >     char  s[3] = &quo

[PATCH] doc: tfix

Remove repeated word (typo). Signed-off-by: Alejandro Colomar --- gcc/doc/extend.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index fd3745c5608..cdfb25ff272 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi

Ping: [PATCH v2] C, ObjC: Add -Wunterminated-string-initialization

Hi David, On 3/24/23 18:58, David Malcolm wrote: > On Fri, 2023-03-24 at 18:45 +0100, Alejandro Colomar wrote: >> Hi David, >> >> On 3/24/23 15:53, David Malcolm wrote: >>> On Fri, 2023-03-24 at 14:39 +0100, Alejandro Colomar via Gcc- >>> patches &

Re: [PATCH v2] C, ObjC: Add -Wunterminated-string-initialization

Hi David, On 3/24/23 15:53, David Malcolm wrote: > On Fri, 2023-03-24 at 14:39 +0100, Alejandro Colomar via Gcc-patches > wrote: >> Warn about the following: >> >>     char  s[3] = "foo"; >> [...] >> --- >> >> Hi, > > Hi Alex,

[PATCH v2] C, ObjC: Add -Wunterminated-string-initialization

rg/archive/html/groff/2022-11/msg00063.html> Link: <https://inbox.sourceware.org/gcc/36da94eb-1cac-5ae8-7fea-ec66160cf...@gmail.com/T/> Acked-by: Doug McIlroy Cc: "G. Branden Robinson" Cc: Ralph Corderoy Cc: Dave Kemper Cc: Larry McVoy Cc: Andrew Pinski Cc: Jonathan Wakely

Re: Ping: [PATCH resend] Make -Wuse-after-free=3 the default one in -Wall

Hi Richard, On 3/15/23 15:52, Richard Biener wrote: > On Wed, Mar 15, 2023 at 3:30 PM Alejandro Colomar via Gcc-patches > wrote: >> >> Ping > > -Wuse-after-free=3 was explicitly added to cover cases with a high > false-positive rate. If you want to > make that

Ping: [PATCH resend] Make -Wuse-after-free=3 the default one in -Wall

Ping On 2/18/23 00:05, Alejandro Colomar wrote: > Link: > <https://inbox.sourceware.org/gcc/3098fd18-9dbf-b4e9-bae5-62ec6fea7...@opteya.com/T/> > Link: <https://github.com/shadow-maint/shadow/pull/649#discussion_r1108350066> > Cc: Andreas Schwab > Cc: David Malcolm

[PATCH resend] Make -Wuse-after-free=3 the default one in -Wall

ly Cc: Mark Wielaard Cc: Martin Uecker Cc: Michael Kerrisk Cc: Paul Eggert Cc: Sam James Cc: Siddhesh Poyarekar Cc: Yann Droneaud Signed-off-by: Alejandro Colomar --- This is a resend of the same patch previously sent to gcc@. gcc/c-family/c.opt | 4 ++-- gcc/doc/invoke.texi | 2 +- 2 f

Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming

On 8/25/22 09:44, Alejandro Colomar wrote: Hi Greg, On 8/25/22 07:57, Greg Kroah-Hartman wrote: On Thu, Aug 25, 2022 at 01:36:10AM +0200, Alejandro Colomar wrote: But from your side what do we have?  Just direct NAKs without much explanation.  The only one who gave some explanation was Greg

Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming

Hi Linus, (Oops, I mistyped you name in my previous reply; I'm on a roll for funny typos this week it seems) On 8/25/22 09:42, Linus Torvalds wrote: On Thu, Aug 25, 2022 at 12:20 AM Alejandro Colomar wrote: This patch is not about kernel, but about the section 2 and 3 manual pages, which

Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming

Hi Xi, On 8/25/22 09:28, Xi Ruoyao wrote: On Thu, 2022-08-25 at 09:20 +0200, Alejandro Colomar via Gcc-patches wrote: I don't know for sure, and I never pretended to say otherwise.  But what IMHO the kernel could do is to make the types compatible, by typedefing to the same fundamental types

Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming

Hi Greg, On 8/25/22 07:57, Greg Kroah-Hartman wrote: On Thu, Aug 25, 2022 at 01:36:10AM +0200, Alejandro Colomar wrote: But from your side what do we have? Just direct NAKs without much explanation. The only one who gave some explanation was Greg, and he vaguely pointed to Linus's comments

Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming

Hi Linux, On 8/25/22 02:52, Linus Torvalds wrote: On Wed, Aug 24, 2022 at 4:36 PM Alejandro Colomar wrote: I'm trying to be nice, and ask for review to make sure I'm not making some big mistake by accident, and I get disrespect? No thanks. You've been told multiple times that the kernel

Re: [PATCH v3] Many pages: Document fixed-width types with ISO C naming

Alexei, On 8/24/22 20:55, Alejandro Colomar wrote: > Link: <https://lore.kernel.org/linux-man/20210423230609.13519-1-alx.manpa...@gmail.com/T/> > Link: <https://lore.kernel.org/lkml/YZvIlz7J6vOEY+Xu@yuki/T/> > Signed-off-by: Alejandro Colomar > Nacked-by: Alex

[PATCH v3] Many pages: Document fixed-width types with ISO C naming

man/20210423230609.13519-1-alx.manpa...@gmail.com/T/> Link: <https://lore.kernel.org/lkml/YZvIlz7J6vOEY+Xu@yuki/T/> Signed-off-by: Alejandro Colomar Nacked-by: Alexei Starovoitov Nacked-by: Greg Kroah-Hartman Nacked-by: Daniel Borkmann Acked-by: Zack Weinberg Cc: LKML Cc: glibc Cc: GCC Cc:

Re: [PATCH v3] bpf.2: Use standard types and attributes

Hello Daniel, On 5/17/21 8:56 PM, Daniel Borkmann wrote: On 5/16/21 11:16 AM, Alejandro Colomar (man-pages) wrote: Signed-off-by: Alejandro Colomar Discussion: <https://lore.kernel.org/linux-man/6740a229-842e-b368-86eb-defc786b3...@gmail.com/T/> Nacked-by: Alexei Starovoitov

Re: [PATCH v3] bpf.2: Use standard types and attributes

On 5/15/21 9:01 PM, Alejandro Colomar wrote: Some manual pages are already using C99 syntax for integral types 'uint32_t', but some aren't. There are some using kernel syntax '__u32'. Fix those. Both the kernel and the standard types are 100% binary compatible, and the source code differences

[PATCH v3] bpf.2: Use standard types and attributes

tps://stackoverflow.com/q/67271825/6872717> Signed-off-by: Alejandro Colomar Nacked-by: Alexei Starovoitov Nacked-by: Greg Kroah-Hartman Acked-by: Zack Weinberg Cc: LKML Cc: glibc Cc: GCC Cc: bpf Cc: David Laight Cc: Joseph Myers Cc: Florian Weimer Cc: Daniel Borkmann --- man2/bpf.

Re: [RFC v2] bpf.2: Use standard types and attributes

ot much of a problem. I'd keep those untouched. Regards, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: [RFC v2] bpf.2: Use standard types and attributes

Hi Florian, On 5/4/21 9:45 PM, Florian Weimer wrote: * Alejandro Colomar: The thing is, in all of those threads, the only reasons to avoid types in the kernel (at least, the only explicitly mentioned ones) are (a bit simplified, but this is the general idea of those threads): * Possibly

Re: [RFC v2] bpf.2: Use standard types and attributes

idea generally.. > I'm trying to clarify the manual pages as much as possible, by using standard conventions and similar structure all around the pages. Not everyone understands kernel conventions. Basically, Zack said very much what I had in mind with this patch. Thanks for your revie

Re: [RFC v2] bpf.2: Use standard types and attributes

callfoo movl%eax, %edx movl$1, %eax subl%edx, %eax ret .cfi_endproc .LFE0: .size main, .-main .ident "GCC: (Debian 10.2.1-6) 10.2.1 20210110" .section.note.GNU-stack,"",@progbits $ --

[RFC v2] bpf.2: Use standard types and attributes

, so the following link is useful in the case of 'alignas()' and '[[gnu::aligned()]]': <https://stackoverflow.com/q/67271825/6872717> Signed-off-by: Alejandro Colomar Cc: LKML Cc: glibc Cc: GCC Cc: Alexei Starovoitov Cc: bpf Cc: David Laight Cc: Zack Weinberg Cc: Joseph Myers --- man2

Re: [RFC] bpf.2: Use standard types and attributes

Hi Joseph, On 4/26/21 7:19 PM, Joseph Myers wrote: On Sat, 24 Apr 2021, Alejandro Colomar via Libc-alpha wrote: Some pages also document attributes, using GNU syntax '__attribute__((xxx))'. Update those to use the shorter and more portable C2x syntax, which hasn't been standardized yet

Re: [RFC] bpf.2: Use standard types and attributes

possible. Any deviation from the standard (be it C or POSIX) should have a very good reason to be; otherwise, it only creates confusion. Thanks, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ Senior SW Engineer; http://www.alejandro-colomar.es/

[RFC] bpf.2: Use standard types and attributes

, which hasn't been standardized yet, but is already implemented in GCC, and available through either --std=c2x or any of the --std=gnu... options. Signed-off-by: Alejandro Colomar --- man2/bpf.2 | 47 +++ 1 file changed, 23 insertions(+), 24 deletions

Ping: [PATCH v6] cacheflush.2: Document __builtin___clear_cache() as a more portable alternative

Ping On 12/15/20 2:30 PM, Alejandro Colomar wrote: > Reported-by: Heinrich Schuchardt > Signed-off-by: Alejandro Colomar > Cc: Martin Sebor > Cc: Dave Martin > --- > > v6: > - GCC has always exposed 'void *', as Martin Sebor noted. > It's Clang (and maybe others)

[PATCH v6] cacheflush.2: Document __builtin___clear_cache() as a more portable alternative

Reported-by: Heinrich Schuchardt Signed-off-by: Alejandro Colomar Cc: Martin Sebor Cc: Dave Martin --- v6: - GCC has always exposed 'void *', as Martin Sebor noted. It's Clang (and maybe others) that (following GCC's docs) exposed 'char *'. man2/cacheflush.2 | 24

[PATCH v5] cacheflush.2: Document __builtin___clear_cache() as a more portable alternative

Reported-by: Heinrich Schuchardt Signed-off-by: Alejandro Colomar --- man2/cacheflush.2 | 24 1 file changed, 24 insertions(+) diff --git a/man2/cacheflush.2 b/man2/cacheflush.2 index aba625721..7a2eed506 100644 --- a/man2/cacheflush.2 +++ b/man2/cacheflush.2 @@ -86,6

Re: [PATCH v4 1/2] system_data_types.7: Add 'void *'

On 10/3/20 9:48 AM, G. Branden Robinson wrote: [...] >> The "short" answer[1] is that I think Alex is correct; Paul's caution is >> unwarranted and arises from confusion with the font alternation macros >> of the man(7) macro package.  Examples of the latter are .BI and .BR. >> Those set their

Re: [PATCH v4 1/2] system_data_types.7: Add 'void *'

Hi Michael and Branden, On 2020-10-03 09:48, G. Branden Robinson wrote: At 2020-10-03T09:10:14+0200, Michael Kerrisk (man-pages) wrote: On 10/2/20 10:27 PM, Alejandro Colomar wrote: On 2020-10-02 22:14, Paul Eggert wrote: > On 10/2/20 11:38 AM, Alejandro Colomar wrote: > >

Re: [PATCH 1/4] system_data_types.7: Add '__int128'

Hi Paul, On 2020-10-02 22:19, Paul Eggert wrote: > On 10/2/20 1:03 PM, Alejandro Colomar wrote: >> I know it's not in stdint, >> but I mean that it behaves as any other stdint type. With caveats, of course. > > It doesn't. There's no portable way to use scanf and printf

Re: [PATCH v4 1/2] system_data_types.7: Add 'void *'

Hi Paul, On 2020-10-02 22:14, Paul Eggert wrote: > On 10/2/20 11:38 AM, Alejandro Colomar wrote: > >> .I void * >> >> renders with a space in between. > > That's odd, as "man(7)" says "All of the arguments will be printed next > to each oth

Re: [PATCH 1/4] system_data_types.7: Add '__int128'

Hi Paul, On 2020-10-02 21:54, Paul Eggert wrote: > On 10/2/20 12:01 PM, Alejandro Colomar wrote: >> If you propose not to document the stdint types either, > > This is not a stdint.h issue. __int128 is not in stdint.h and is not a > system data type in any real sense; it's

[PATCH v5 1/2] system_data_types.7: Add 'void *'

Signed-off-by: Alejandro Colomar system_data_types.7: void *: Add info about generic function parameters and return value Reported-by: Paul Eggert Reported-by: David Laight Signed-off-by: Alejandro Colomar system_data_types.7: void *: Add info about pointer artihmetic Reported-by: Paul

[PATCH v5 2/2] void.3: New link to system_data_types(7)

Signed-off-by: Alejandro Colomar --- man3/void.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/void.3 diff --git a/man3/void.3 b/man3/void.3 new file mode 100644 index 0..db50c0f09 --- /dev/null +++ b/man3/void.3 @@ -0,0 +1 @@ +.so man7/system_data_types.7 -- 2.28.0

[PATCH v5 0/2] Document 'void *'

), memcmp(3), memcpy(3), memset(3) See also the intptr_t and uintptr_t types in this page. ]] Alejandro Colomar (2): system_data_types.7: Add 'void *' void.3: New link to system_data_types(7) man3/void.3 | 1 + man7/system_data_types.7 | 76

Re: [PATCH 1/4] system_data_types.7: Add '__int128'

Hi Paul, On 2020-10-02 19:52, Paul Eggert wrote: Why describe __int128_t in these man pages at all? __int128_t is not a property of either the kernel or of glibc, so it's out of scope. Well, as I see it, [unsigned] __int128 is as good as [u]int64_t. They are part of the C interface in Linux.

Re: [PATCH v4 1/2] system_data_types.7: Add 'void *'

Hi Paul, On 2020-10-02 18:53, Paul Eggert wrote: > On 10/2/20 8:14 AM, Alejandro Colomar wrote: > >> +.I void * > > GNU style is a space between "void" and "*", so this should be '.I > "void\ *"', both here and elsewhere. The backslash prev

[PATCH v4 2/2] void.3: New link to system_data_types(7)

Signed-off-by: Alejandro Colomar --- man3/void.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/void.3 diff --git a/man3/void.3 b/man3/void.3 new file mode 100644 index 0..db50c0f09 --- /dev/null +++ b/man3/void.3 @@ -0,0 +1 @@ +.so man7/system_data_types.7 -- 2.28.0

[PATCH v4 1/2] system_data_types.7: Add 'void *'

Signed-off-by: Alejandro Colomar system_data_types.7: void *: Add info about generic function parameters and return value Reported-by: Paul Eggert Reported-by: David Laight Signed-off-by: Alejandro Colomar system_data_types.7: void *: Add info about pointer artihmetic Reported-by: Paul

[PATCH v4 0/2] Document 'void *'

it v4). Regards, Alex Alejandro Colomar (2): system_data_types.7: Add 'void *' void.3: New link to system_data_types(7) man3/void.3 | 1 + man7/system_data_types.7 | 80 +++- 2 files changed, 79 insertions(+), 2 deletions(-) create mode 100644

[PATCH v2 2/4] __int128.3: New link to system_data_types(7)

Signed-off-by: Alejandro Colomar --- man3/__int128.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/__int128.3 diff --git a/man3/__int128.3 b/man3/__int128.3 new file mode 100644 index 0..db50c0f09 --- /dev/null +++ b/man3/__int128.3 @@ -0,0 +1 @@ +.so man7

[PATCH v2 4/4] unsigned-__int128.3: New link to system_data_types(7)

Signed-off-by: Alejandro Colomar --- man3/unsigned-__int128.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/unsigned-__int128.3 diff --git a/man3/unsigned-__int128.3 b/man3/unsigned-__int128.3 new file mode 100644 index 0..db50c0f09 --- /dev/null +++ b/man3/unsigned

[PATCH v2 3/4] system_data_types.7: Add 'unsigned __int128'

Signed-off-by: Alejandro Colomar --- man7/system_data_types.7 | 35 +++ 1 file changed, 35 insertions(+) diff --git a/man7/system_data_types.7 b/man7/system_data_types.7 index 5f9aa648f..3cf3f0ec9 100644 --- a/man7/system_data_types.7 +++ b/man7/system_data_types

[PATCH v2 1/4] system_data_types.7: Add '__int128'

Signed-off-by: Alejandro Colomar --- man7/system_data_types.7 | 40 1 file changed, 40 insertions(+) diff --git a/man7/system_data_types.7 b/man7/system_data_types.7 index e545aa1a0..5f9aa648f 100644 --- a/man7/system_data_types.7 +++ b/man7

[PATCH v2 0/4] Document 128-bit types

Hi Michael, I fixed the stray '"' noticed by Florian. Cheers, Alex Alejandro Colomar (4): system_data_types.7: Add '__int128' __int128.3: New link to system_data_types(7) system_data_types.7: Add 'unsigned __int128' unsigned-__int128.3: New link to system_data_types(7)

[PATCH 2/2] void.3: New link to system_data_types(7)

Signed-off-by: Alejandro Colomar --- man3/void.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/void.3 diff --git a/man3/void.3 b/man3/void.3 new file mode 100644 index 0..db50c0f09 --- /dev/null +++ b/man3/void.3 @@ -0,0 +1 @@ +.so man7/system_data_types.7 -- 2.28.0

[PATCH 1/2] system_data_types.7: Add 'void *'

Signed-off-by: Alejandro Colomar system_data_types.7: void *: Add info about generic function parameters and return value Reported-by: Paul Eggert Reported-by: David Laight Signed-off-by: Alejandro Colomar system_data_types.7: void *: Add info about pointer artihmetic Reported-by: Paul

[PATCH 0/2] Document 'void *'

Hi Michael, As you asked, I squashed. And added the POSIX.1-2008 note too. Thanks for that! Cheers, Alex Alejandro Colomar (2): system_data_types.7: Add 'void *' void.3: New link to system_data_types(7) man3/void.3 | 1 + man7/system_data_types.7 | 80

Re: [PATCH 2/2] system_data_types.7: void *: Add info about pointer artihmetic

Hi Michael, The 2/2 is a typo. This is a standalone patch. Cheers, Alex On 2020-10-02 11:44, Alejandro Colomar wrote: Reported-by: Paul Eggert Reported-by: David Laight Signed-off-by: Alejandro Colomar --- Paul and David, Thanks for your input! Alex man7/system_data_types.7 | 11

[PATCH 2/2] system_data_types.7: void *: Add info about pointer artihmetic

Reported-by: Paul Eggert Reported-by: David Laight Signed-off-by: Alejandro Colomar --- Paul and David, Thanks for your input! Alex man7/system_data_types.7 | 11 +++ 1 file changed, 11 insertions(+) diff --git a/man7/system_data_types.7 b/man7/system_data_types.7 index 6451782db

[PATCH] system_data_types.7: void *: Add info about generic function parameters and return value

Reported-by: Paul Eggert Reported-by: David Laight Signed-off-by: Alejandro Colomar --- Paul and David, Thanks for your input! Alex man7/system_data_types.7 | 16 1 file changed, 16 insertions(+) diff --git a/man7/system_data_types.7 b/man7/system_data_types.7 index

[PATCH 1/4] system_data_types.7: Add '__int128'

Signed-off-by: Alejandro Colomar --- man7/system_data_types.7 | 40 1 file changed, 40 insertions(+) diff --git a/man7/system_data_types.7 b/man7/system_data_types.7 index e545aa1a0..5f9aa648f 100644 --- a/man7/system_data_types.7 +++ b/man7

[PATCH 2/4] __int128.3: New link to system_data_types(7)

Signed-off-by: Alejandro Colomar --- man3/__int128.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/__int128.3 diff --git a/man3/__int128.3 b/man3/__int128.3 new file mode 100644 index 0..db50c0f09 --- /dev/null +++ b/man3/__int128.3 @@ -0,0 +1 @@ +.so man7

[PATCH 3/4] system_data_types.7: Add 'unsigned __int128'

Signed-off-by: Alejandro Colomar --- man7/system_data_types.7 | 35 +++ 1 file changed, 35 insertions(+) diff --git a/man7/system_data_types.7 b/man7/system_data_types.7 index 5f9aa648f..3cf3f0ec9 100644 --- a/man7/system_data_types.7 +++ b/man7/system_data_types

[PATCH 0/4] Document 128-bit types

Hi Michael, I think this might be ready for a patch. I'm done for today :-) Cheers, Alex Alejandro Colomar (4): system_data_types.7: Add '__int128' __int128.3: New link to system_data_types(7) system_data_types.7: Add 'unsigned __int128' unsigned-__int128.3: New link

[PATCH 4/4] unsigned-__int128.3: New link to system_data_types(7)

Signed-off-by: Alejandro Colomar --- man3/unsigned-__int128.3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 man3/unsigned-__int128.3 diff --git a/man3/unsigned-__int128.3 b/man3/unsigned-__int128.3 new file mode 100644 index 0..db50c0f09 --- /dev/null +++ b/man3/unsigned