public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Lukasz Majewski <lukma@denx.de>
Cc: Florian Weimer <fweimer@redhat.com>,
	 GNU C Library <libc-alpha@sourceware.org>,
	 Stepan Golosunov <stepan@golosunov.pp.ru>,
	Alistair Francis <alistair.francis@wdc.com>,
	 Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH] [RFC] y2038: nptl: Convert pthread_cond_{clock|timed}wait to support 64 bit time
Date: Tue, 25 Aug 2020 12:34:29 +0200	[thread overview]
Message-ID: <871rjvxbd6.fsf@igel.home> (raw)
In-Reply-To: <20200825120324.74c9ad99@jawa> (Lukasz Majewski's message of "Tue, 25 Aug 2020 12:03:24 +0200")

On Aug 25 2020, Lukasz Majewski wrote:

> Hi Andreas,
>
>> On Aug 24 2020, Lukasz Majewski wrote:
>> 
>> > diff --git a/sysdeps/unix/sysv/linux/m68k/Makefile
>> > b/sysdeps/unix/sysv/linux/m68k/Makefile index
>> > be40fae68a..f19c8c825d 100644 ---
>> > a/sysdeps/unix/sysv/linux/m68k/Makefile +++
>> > b/sysdeps/unix/sysv/linux/m68k/Makefile @@ -21,3 +21,8 @@
>> > sysdep-dl-routines += dl-static sysdep-others += lddlibc4
>> >  install-bin += lddlibc4
>> >  endif
>> > +
>> > +ifeq ($(subdir),nptl)
>> > +libpthread-sysdep_routines += futex-helpers  
>> 
>> Why do you need that twice?
>
> This is to fix following issue:
> https://marc.info/?l=glibc-alpha&m=159730587416436&w=2

But why *twice*?

>> 
>> > +CFLAGS-futex-helpers.c += -fno-inline  
>> 
>> Why do you need that?
>
> This solves problem with small number general purpose registers on m68k
> when inlining this patch.

What do you mean with "inlining this patch"?

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2020-08-25 10:34 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 [this message]
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
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=871rjvxbd6.fsf@igel.home \
    --to=schwab@suse.de \
    --cc=alistair.francis@wdc.com \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=lukma@denx.de \
    --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).