From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [RFC] final time64 switch-over patch series
Date: Sun, 4 Aug 2019 00:31:09 -0400 [thread overview]
Message-ID: <20190804043109.GL9017@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190802214433.GA25193@brightrain.aerifal.cx>
On Fri, Aug 02, 2019 at 05:44:33PM -0400, Rich Felker wrote:
> >From 3c6bde03ecf2aa7dac605f0a55a1be201f3d4c5f Mon Sep 17 00:00:00 2001
> From: Rich Felker <dalias@aerifal.cx>
> Date: Fri, 2 Aug 2019 15:41:27 -0400
> Subject: [PATCH 5/5] [RFC] [POC] switch i386 to 64-bit time_t
>
> this is a proof of concept for converting one 32-bit arch, i386, to
> 64-bit time_t. known issues:
>
> 1. the switchover of timespec padding is a hack, and needs to be done
> right, but that involves making alltypes.h aware of endianness, which
> probably should have been done a long time ago anyway and would get
> rid of inappropriate inclusion of <endian.h> in some places.
>
> 2. the rusage, utmpx, and timex structs are not correct with regard to
> ABI or functionality. they need to be fixed before this is safe to
> use.
>
> 3. Makefile change should be its own thing.
>
> there are likely a lot more problems.
Add a significant incomplete prerequisite I forgot about: dlsym. There
needs to be a redirection for dlsym, and 32-bit archs need a second
asm entry point for __dlsym_time64 which first checks the symbol name
against the list of time64 redirections and rewrites the request if
it's a match.
Rich
next prev parent reply other threads:[~2019-08-04 4:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 21:44 Rich Felker
2019-08-04 4:31 ` Rich Felker [this message]
2019-08-09 16:30 ` Rich Felker
2019-08-09 17:00 ` Rich Felker
2019-08-04 4:33 ` Rich Felker
2019-08-04 18:11 ` Rich Felker
2019-08-09 14:48 ` Rich Felker
2019-08-14 23:55 ` Rich Felker
2019-08-15 0:13 ` Rich Felker
2019-08-15 0:30 ` Rich Felker
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=20190804043109.GL9017@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).