public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] manual: fix order of arguments of memalign and aligned_alloc (Bug 27547) Date: Wed, 24 Jan 2024 17:12:42 +0000 (GMT) [thread overview] Message-ID: <20240124171242.E62343858C52@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c06c8aeb61708249d8eb0b17a676d16771ea640b commit c06c8aeb61708249d8eb0b17a676d16771ea640b Author: Dennis Brendel <dbrendel@redhat.com> Date: Mon Jan 15 09:55:37 2024 +0100 manual: fix order of arguments of memalign and aligned_alloc (Bug 27547) On the summary page the order of the function arguments was reversed, but it is in correct order in the other places of the manual. Reviewed-by: Carlos O'Donell <carlos@redhat.com> Diff: --- manual/memory.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/manual/memory.texi b/manual/memory.texi index fb875f4c3c..3710d7ec66 100644 --- a/manual/memory.texi +++ b/manual/memory.texi @@ -1502,7 +1502,7 @@ Space}. Allocate a block of @var{size} bytes, starting on a page boundary. @xref{Aligned Memory Blocks}. -@item void *aligned_alloc (size_t @var{size}, size_t @var{alignment}) +@item void *aligned_alloc (size_t @var{alignment}, size_t @var{size}) Allocate a block of @var{size} bytes, starting on an address that is a multiple of @var{alignment}. @xref{Aligned Memory Blocks}. @@ -1510,7 +1510,7 @@ multiple of @var{alignment}. @xref{Aligned Memory Blocks}. Allocate a block of @var{size} bytes, starting on an address that is a multiple of @var{alignment}. @xref{Aligned Memory Blocks}. -@item void *memalign (size_t @var{size}, size_t @var{boundary}) +@item void *memalign (size_t @var{boundary}, size_t @var{size}) Allocate a block of @var{size} bytes, starting on an address that is a multiple of @var{boundary}. @xref{Aligned Memory Blocks}.
reply other threads:[~2024-01-24 17:12 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20240124171242.E62343858C52@sourceware.org \ --to=carlos@sourceware.org \ --cc=glibc-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).