From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Andreas Schwab <schwab@linux-m68k.org>,
Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] [RFC] y2038: nptl: Convert pthread_cond_{clock|timed}wait to support 64 bit time
Date: Tue, 25 Aug 2020 12:36:15 -0300 [thread overview]
Message-ID: <9e38b28a-52ea-7661-f8ed-e82987f6b0dd@linaro.org> (raw)
In-Reply-To: <664bfc3a-6d6f-65b8-942a-44861f687c02@linaro.org>
On 25/08/2020 12:31, Adhemerval Zanella wrote:
>
>
> On 25/08/2020 12:26, Andreas Schwab wrote:
>> On Aug 25 2020, Adhemerval Zanella via Libc-alpha wrote:
>>
>>> On 25/08/2020 11:47, Andreas Schwab wrote:
>>>> On Aug 25 2020, Lukasz Majewski wrote:
>>>>
>>>>> When I put futex_abstimed_wait_cancelable64() as static __always_inline
>>>>> to futex-internals.h then the aforementioned problem on m68k emerge.
>>>>
>>>> But futex-helpers.c contains a single function. There is nothing to
>>>> inline.
>>>>
>>>> Andreas.
>>>>
>>>
>>> in_time_t_range and valid_timespec64_to_timespec.
>>
>> But you don't want to uninline them.
>
> Yes, that it seems exactly what is triggering gcc ICE.
>
And my suggestion to try workaround this issue is to move 32-bit futex call to
its own function [1].
[1] https://sourceware.org/pipermail/libc-alpha/2020-August/117254.html
next prev parent reply other threads:[~2020-08-25 15:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 16:40 Lukasz Majewski
2020-08-24 16:59 ` Lukasz Majewski
2020-08-24 17:15 ` Florian Weimer
2020-08-24 17:50 ` Lukasz Majewski
2020-08-25 8:08 ` Andreas Schwab
2020-08-25 10:03 ` Lukasz Majewski
2020-08-25 10:34 ` Andreas Schwab
2020-08-25 14:29 ` Adhemerval Zanella
2020-08-25 14:30 ` Lukasz Majewski
2020-08-25 14:47 ` Andreas Schwab
2020-08-25 14:53 ` Adhemerval Zanella
2020-08-25 15:26 ` Andreas Schwab
2020-08-25 15:31 ` Adhemerval Zanella
2020-08-25 15:36 ` Adhemerval Zanella [this message]
2020-08-25 14:43 ` Adhemerval Zanella
2020-08-26 17:59 ` Lukasz Majewski
2020-08-26 18:06 ` Florian Weimer
2020-08-26 19:38 ` Adhemerval Zanella
2020-08-27 6:20 ` Lukasz Majewski
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=9e38b28a-52ea-7661-f8ed-e82987f6b0dd@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).