unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Wolfgang Denk <wd@denx.de>
Cc: libc-alpha@sourceware.org,  Lukasz Majewski <lukma@denx.de>
Subject: Re: Accelerating Y2038 glibc fixes
Date: Tue, 16 Jul 2019 17:09:26 +0200	[thread overview]
Message-ID: <87muheggnt.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20190716145216.1C7CE240085@gemini.denx.de> (Wolfgang Denk's message of "Tue, 16 Jul 2019 16:52:16 +0200")

* Wolfgang Denk:

> In message <874l3mjgi6.fsf@oldenburg2.str.redhat.com> you wrote:
>>
>> One difficult trade-off is that for you, this is just one-time
>> enablement work, but the regular contributors will be stuck with the
>> code you add forever.  Especially since it touches 64-bit architectures
>> as well.
>
> I am aware of this, and I'm willing to go all necessary procedures
> to get things right.  If someone points out a problem, we can
> address it, and move on.  But we haven't seen any progress for a
> long time...

This is not what I meant, or maybe I'm misunderstanding you.  Are you
offering a long-term collaboration on a varied range of topics?  Or just
this one contribution of a single feature?

>> For me personally, the whole project is quite baffling.  I'm interested
>> in 32-bit changes only to support legacy binaries, and this is new work
>> targeting new binaries.
>
> Indeed it is easy for all the big distros who dropped (at least
> commercial) support for 32 bit systems years ago.

Red Hat still supports 32-bit legacy applications.  I'm sure SUSE does
as well.

Newer operating system releases do not come with a 32-bit kernel
anymore, but we have a 32-bit userspace (mostly consisting of libraries
to support existing legacy application), so we still need glibc.

> I think this is part of the problem - the big distros are not really
> interested in this work, they see it only as a nuisance to their
> business cases.  I cannot stop myself from stating that such an
> approach is egotistic at best, if not ignorant, or both.

I would even go one step further: For i386, the upcoming ABI
fragmentation impacts our users even if they are never going to use the
new capabilities.

There also appears to be an expectation that all applications which
invoke the futex system call directly need to be changed at the source
code level.  This will affect many upstream projects, even if they
primarily target 64-bit architectures.

Thanks,
Florian

  reply	other threads:[~2019-07-16 15:09 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  7:21 Accelerating Y2038 glibc fixes Wolfgang Denk
2019-07-16  9:32 ` Wolfgang Denk
2019-07-16 11:50 ` Siddhesh Poyarekar
2019-07-16 12:40   ` Wolfgang Denk
2019-07-16 12:44 ` Florian Weimer
2019-07-16 14:52   ` Wolfgang Denk
2019-07-16 15:09     ` Florian Weimer [this message]
2019-07-16 15:19       ` Andrew Pinski
2019-07-17 14:15     ` Arnd Bergmann
2019-07-17 14:41       ` Florian Weimer
2019-07-17 16:00         ` Wolfgang Denk
2019-07-17 16:04           ` Florian Weimer
2019-07-17 16:18             ` Lukasz Majewski
2019-07-18 18:53               ` Adhemerval Zanella
2019-07-18 19:13                 ` Florian Weimer
2019-07-18 20:31                   ` Adhemerval Zanella
2019-07-18 21:20                     ` Florian Weimer
2019-07-18 22:32                     ` Paul Eggert
2019-07-19  7:21                       ` Andreas Schwab
2019-07-19  3:06                     ` Rich Felker
2019-07-19 17:44                       ` Adhemerval Zanella
2019-07-19 19:03                         ` Alistair Francis
2019-07-25 20:40                 ` Joseph Myers
2019-07-29 17:47                   ` Adhemerval Zanella
2019-07-29 19:58                     ` Joseph Myers
2019-07-29 21:00                       ` Adhemerval Zanella
2019-07-29 21:08                         ` Joseph Myers
2019-07-29 23:12                           ` Paul Eggert
2019-07-29 23:30                             ` Joseph Myers
2019-07-17 17:50       ` Rich Felker
2019-07-17 21:57         ` Lukasz Majewski
2019-07-17 22:37           ` Rich Felker
2019-07-18  7:20             ` Lukasz Majewski
2019-07-18 13:35               ` Rich Felker
2019-07-18 14:47           ` Rich Felker
2019-07-18 14:49             ` Florian Weimer
2019-07-18 15:46               ` Rich Felker
2019-07-18 16:43                 ` Adhemerval Zanella
2019-07-20  4:43             ` Rich Felker
2019-07-25 19:54 ` Joseph Myers
2019-07-26 10:39   ` Lukasz Majewski
2019-07-29 18:55     ` Zack Weinberg
2019-07-29 20:12       ` Joseph Myers
2019-07-30 11:02         ` Lukasz Majewski
2019-07-30 12:24           ` Joseph Myers
2019-07-30 14:04       ` Lukasz Majewski
2019-08-09  7:25         ` Lukasz Majewski
     [not found]           ` <CAKCAbMhOMQ9yTFpy+OQkDvZPPFf_fFn6oSxjvLTaUwC4jpPRag@mail.gmail.com>
2019-08-09 12:32             ` Fwd: " Zack Weinberg
2019-07-30 19:58       ` Joseph Myers
2019-07-30 20:28         ` Florian Weimer

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87muheggnt.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=lukma@denx.de \
    --cc=wd@denx.de \
    /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).