public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/8] Consolidate Linux open implementation
Date: Mon, 15 May 2017 13:01:00 -0000	[thread overview]
Message-ID: <2af58a25-46e9-af92-cf4d-cb3bbb24b0c8@linaro.org> (raw)
In-Reply-To: <87tw4mxp65.fsf@totoro.br.ibm.com>



On 15/05/2017 09:47, Tulio Magno Quites Machado Filho wrote:
> Adhemerval Zanella <adhemerval.zanella@linaro.org> writes:
> 
>> This patch consolidates the open Linux syscall implementation on
>> sysdeps/unix/sysv/linux/open{64}.c.  The changes are:
>>
>>   1. Remove open{64} from auto-generation syscalls.list.
>>   2. Add a new open{64}.c implementation.  For architectures that
>>      define __OFF_T_MATCHES_OFF64_T the default open64 will create
>>      alias to required open symbols.
>>   3. Use __NR_open where possible, otherwise use __NR_openat.
>>
>> Checked on i686-linux-gnu, x86_64-linux-gnu, x86_64-linux-gnux32,
>> arch64-linux-gnu, arm-linux-gnueabihf, and powerpc64le-linux-gnu.
>>
>> 	* sysdeps/unix/sysv/linux/generic/open.c: Remove file.
>> 	* sysdeps/unix/sysv/linux/generic/open64.c: Likewise.
>> 	* sysdeps/unix/sysv/linux/wordsize-64/open64.c: Likewise.
>> 	* sysdeps/unix/sysv/linux/open.c: New file.
>> 	* sysdeps/unix/sysv/linux/open64.c (__libc_open64): Use O_LARGEFILE
>> 	only for __OFF_T_MATCHES_OFF64_T and add alias to open if the case.
>> 	* sysdeps/unix/sysv/linux/wordsize-64/syscalls.list: Remove open
>> 	from auto-generated list.
> 
> For the record: there was a build error in our POWER8 BuildSlave right after
> this patch was merged [1].
> 
> I was not able to reproduce this error on my servers and I suspect it might
> be related to issues in our BuildBot setup which may still be leaving
> old files before starting a new build.
> 
> This patch is not related to the failures on build 464 on the same builder.
> 
> [1] http://144.217.14.79/builders/glibc-power8-linux/builds/463
> 

It is unexpected because I did checked natively on powerpc64le-linux-gnu
(power8) and also on cross-compiling using build-many-glibc.py.

  reply	other threads:[~2017-05-15 13:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08 15:27 [PATCH 1/8] Consolidate Linux close syscall generation Adhemerval Zanella
2017-05-08 15:27 ` [PATCH 5/8] Consolidate Linux write syscall Adhemerval Zanella
2017-05-11 15:21   ` Andreas Schwab
2017-05-08 15:27 ` [PATCH 6/8] Consolidate Linux readv implementation Adhemerval Zanella
2017-05-11 15:33   ` Andreas Schwab
2017-05-08 15:27 ` [PATCH 2/8] Consolidate Linux open implementation Adhemerval Zanella
2017-05-11 15:06   ` Andreas Schwab
2017-05-11 15:20     ` Adhemerval Zanella
2017-05-15 12:47   ` Tulio Magno Quites Machado Filho
2017-05-15 13:01     ` Adhemerval Zanella [this message]
2017-05-08 15:27 ` [PATCH 3/8] Consolidate Linux creat implementation Adhemerval Zanella
2017-05-11 15:16   ` Andreas Schwab
2017-05-11 15:21     ` Adhemerval Zanella
2017-05-08 15:27 ` [PATCH 4/8] Consolidate Linux read syscall Adhemerval Zanella
2017-05-11 15:17   ` Andreas Schwab
2017-05-08 15:27 ` [PATCH 8/8] powerpc: Fix signal handling in backtrace Adhemerval Zanella
2017-05-09 12:11   ` Tulio Magno Quites Machado Filho
2017-05-09 13:13     ` Adhemerval Zanella
2017-05-08 15:27 ` [PATCH 7/8] Consolidate Linux writev implementation Adhemerval Zanella
2017-05-11 15:33   ` Andreas Schwab
2017-05-11 14:48 ` [PATCH 1/8] Consolidate Linux close syscall generation Andreas Schwab

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=2af58a25-46e9-af92-cf4d-cb3bbb24b0c8@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --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).