public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: libc-alpha@sourceware.org
Cc: Steve Ellcey <sellcey@caviumnetworks.com>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH v3 00/17] Consolidate Linux sysvipc implementation
Date: Fri, 09 Dec 2016 20:04:00 -0000	[thread overview]
Message-ID: <10763878.Gf8T87Klc7@wuerfel> (raw)
In-Reply-To: <1481308253.29811.77.camel@caviumnetworks.com>

On Friday, December 9, 2016 10:30:53 AM CET Steve Ellcey wrote:
> 
> Adhemerval,
> 
> It looks like you may have to tweek your change to test-skeleton.c in
> this patch.  The FAIL_EXIT macro was moved from test-skeleton.c
> to support/check.h so I assume your new FAIL_UNSUPPORTED macro should
> be moved there as well.
> 
> I have been doing aarch64 and x86 builds here with your patch and have
> not had any problems except with my new aarch64 ILP32 code.  There I
> had to change the definition of __IPC_64 in the new header
> file sysdeps/unix/sysv/linux/aarch64/ipc_priv.h from:
> 
> #define __IPC_64     0x0
> 
> to:
> 
> #ifdef __LP64__
> # define __IPC_64     0x0
> #else /* __ILP32  */
> # define __IPC_64     0x100
> #endif

Huh?

I would hope that this is not really needed, it looks like
a kernel bug. The old style IPC has been deprecated for so
long that nothing should need to pass the 0x100 flag, unless
it dates back to the last century.

Do we need to override the version parsing in the kernel?

	Arnd

  reply	other threads:[~2016-12-09 20:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 20:30 Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 04/17] Consolidate Linux msgrcv implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 03/17] Consolidate Linux msgctl implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 01/17] Add __ASSUME_SYSVIPC_SYSCALL for Linux Adhemerval Zanella
2016-11-08 21:19   ` Andreas Schwab
2016-11-09 13:23     ` Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 10/17] Use semop syscall for Linux implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 02/17] Refactor Linux ipc_priv header Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 13/17] Use shmat syscall for Linux implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 15/17] Use shmdt syscall for linux implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 11/17] Consolidate Linux semtimedop implementation Adhemerval Zanella
2016-11-08 20:30 ` [PATCH v3 12/17] Add SYSV semaphore test Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 09/17] Use semget syscall for Linux implementation Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 05/17] Use msgsnd " Adhemerval Zanella
2016-11-08 21:13   ` Andreas Schwab
2016-11-09 13:23     ` Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 14/17] Consolidate Linux shmctl implementation Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 17/17] Add SYSV shared memory test Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 16/17] Use shmget syscall for linux implementation Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 08/17] Consolidate Linux semctl implementation Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 07/17] Add SYSV message queue test Adhemerval Zanella
2016-11-08 21:23   ` Andreas Schwab
2016-11-09 13:28     ` Adhemerval Zanella
2016-11-08 20:31 ` [PATCH v3 06/17] Use msgget syscall for Linux implementation Adhemerval Zanella
2016-11-09 13:57 ` [PATCH v3 00/17] Consolidate Linux sysvipc implementation Yury Norov
2016-11-25 14:02 ` Adhemerval Zanella
2016-12-07 19:14   ` Adhemerval Zanella
2016-12-09 18:31     ` Steve Ellcey
2016-12-09 20:04       ` Arnd Bergmann [this message]
2017-01-05 20:57         ` Yury Norov
2016-12-09 20:18       ` Adhemerval Zanella

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=10763878.Gf8T87Klc7@wuerfel \
    --to=arnd@arndb.de \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=sellcey@caviumnetworks.com \
    /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).