From: Dennis Brendel <dbrendel@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH] Manual: fix order of arguments of memalign and aligned_alloc
Date: Mon, 15 Jan 2024 09:55:37 +0100 [thread overview]
Message-ID: <779c4fcc-5dc9-4bc1-9d68-cbce31a0d8e7@redhat.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1297 bytes --]
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.
BZ #27547
---
manual/memory.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/manual/memory.texi b/manual/memory.texi
index 258fdbd3a0..78b657627f 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}.
--
2.43.0
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3195 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next reply other threads:[~2024-01-15 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 8:55 Dennis Brendel [this message]
2024-01-24 16:25 ` Carlos O'Donell
2024-01-24 16:42 ` Andreas K. Huettel
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=779c4fcc-5dc9-4bc1-9d68-cbce31a0d8e7@redhat.com \
--to=dbrendel@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).