mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Felix Mellmann <flix.ptxdist@benfm.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2021.07.0 released
Date: Mon, 12 Jul 2021 08:48:05 +0200	[thread overview]
Message-ID: <20210712064805.GA27936@pengutronix.de> (raw)
In-Reply-To: <40f2ae97-36f0-6cf0-915a-253cafd69a3e@benfm.de>

Hi,

I've put the list back in Cc. I think this is interesting for others as
well.

On Sun, Jul 11, 2021 at 02:00:33PM +0200, Felix Mellmann wrote:
> thanks for releasing an updated toolchain!
> 
> Do the ARM 32bit toolchains already make use of the 64 bit unix timestamps
> to overcome the 2k38 problem?

I assume you mean the compat stuff where time_t is 64 bit (with _TIME_BITS
defined).
No. The support for this is still missing in glibc 2.33. I looked into this
when I was working on the toolchains and at the time, there where quite a
few patches that had not been merged for this. From what I can tell, they
have been merged in the meantime. I've not checked if there are still some
bits missing. But I hope that glibc 2.34 will have the full support.

> As far as I can see, glibc is compiled against the kernel 3.16 headers which
> do not include support for 64 bit timestamps on 32 bit machines (https://git.pengutronix.de/cgit/OSELAS.Toolchain/tree/ptxconfigs/arm-v7a-linux-gnueabihf_gcc-11.1.1_clang-12.0.0_glibc-2.33_binutils-2.36.1_kernel-5.12.4-sanitized.ptxconfig?h=v2021.07.0
> , line 51)

That's something else. The toolchain is built with 5.12.4 kernel headers
(line 62). The PTXCONF_GLIBC_ENABLE_KERNEL specifies the oldest kernel this
glibc will run on. Basically how much compat code should be added for
syscalls etc. that did not exist in old kernel versions.

> If the toolchain still uses 32 bit timestamps - are there any plans to
> implement support in an upcoming release?

Yes definitively. Right now I'm still waiting for a glibc release that has
the necessary support. I don't think we actually need to do anything here.
At least in the toolchain. It should just work once we have a glibc that
supports it.

I think the hard part will be all the other userspace software. We need to
compile it with _TIME_BITS (and _FILE_OFFSET_BITS=64). That's the easy
part. But someone need to check all the code to check that time_t is never
cast to/from int...

Regards,
Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


      parent reply	other threads:[~2021-07-12  6:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06  7:52 Michael Olbrich
     [not found] ` <40f2ae97-36f0-6cf0-915a-253cafd69a3e@benfm.de>
2021-07-12  6:48   ` Michael Olbrich [this message]

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=20210712064805.GA27936@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=flix.ptxdist@benfm.de \
    --cc=ptxdist@pengutronix.de \
    --subject='Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2021.07.0 released' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox