From: Andreas Schwab <schwab@linux-m68k.org>
To: Alistair Francis via Libc-alpha <libc-alpha@sourceware.org>
Cc: Alistair Francis <alistair.francis@wdc.com>, stepan@golosunov.pp.ru
Subject: Re: [PATCH v8 2/2] sysv: linux: Pass 64-bit version of semctl syscall
Date: Wed, 27 May 2020 17:38:41 +0200 [thread overview]
Message-ID: <87y2pdwfpa.fsf@igel.home> (raw)
In-Reply-To: <20200513152249.5103-3-alistair.francis@wdc.com> (Alistair Francis via Libc-alpha's message of "Wed, 13 May 2020 08:22:49 -0700")
On Mai 13 2020, Alistair Francis via Libc-alpha wrote:
> diff --git a/sysdeps/unix/sysv/linux/ipc_priv.h b/sysdeps/unix/sysv/linux/ipc_priv.h
> index 15a6e683a4..a1a7cacd17 100644
> --- a/sysdeps/unix/sysv/linux/ipc_priv.h
> +++ b/sysdeps/unix/sysv/linux/ipc_priv.h
> @@ -43,6 +43,10 @@ struct __old_ipc_perm
> unsigned short int __seq; /* Sequence number. */
> };
>
> +#define __IPC_TIME64 \
> + (__WORDSIZE == 32 && __TIMESIZE == 64 \
> + && (!defined __SYSCALL_WORDSIZE || __SYSCALL_WORDSIZE == 32))
Using defined in a macro expansion is undefined.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-05-27 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 15:22 [PATCH v8 0/2] Support semctl_syscall() for __TIMESIZE==64 Alistair Francis
2020-05-13 15:22 ` [PATCH v8 1/2] sysv: linux: Define the __semid_ds32 struct Alistair Francis
2020-05-13 15:22 ` [PATCH v8 2/2] sysv: linux: Pass 64-bit version of semctl syscall Alistair Francis
2020-05-27 15:38 ` Andreas Schwab [this message]
2020-06-01 1:44 ` Alistair Francis
2020-05-27 1:42 ` [PATCH v8 0/2] Support semctl_syscall() for __TIMESIZE==64 Vineet Gupta
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=87y2pdwfpa.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=alistair.francis@wdc.com \
--cc=libc-alpha@sourceware.org \
--cc=stepan@golosunov.pp.ru \
/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).