Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <1576797980.31912.110.camel@zv.io>
Subject: Re: [PATCH v5 6/8] media: v4l2-core: fix v4l2_buffer handling for
 time64 ABI
From:   Zach van Rijn <me@zv.io>
To:     Arnd Bergmann <arnd@arndb.de>, Hans Verkuil <hverkuil@xs4all.nl>
Cc:     Linux Media Mailing List <linux-media@vger.kernel.org>,
        Mauro Carvalho Chehab <mchehab@kernel.org>,
        y2038 Mailman List <y2038@lists.linaro.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Date:   Thu, 19 Dec 2019 17:26:20 -0600
In-Reply-To: <CAK8P3a1-xLUn368Lajia1=2GEXa92srQ2s9wH--MrRHj+kSTtQ@mail.gmail.com>
References: <20191126161824.337724-1-arnd@arndb.de>
         <20191126161824.337724-7-arnd@arndb.de>
         <09c664fd-87fb-4fac-f104-9afbe7d33aa2@xs4all.nl>
         <CAK8P3a1TvFCJf8t9T1yOXjsp088s9dbEOKLVDPinfwJe2B-27g@mail.gmail.com>
         <81bb5da1-6b84-8473-4ada-c174f43bbae2@xs4all.nl>
         <0843718f-1391-3379-38be-41fa9558ea6d@xs4all.nl>
         <CAK8P3a1-xLUn368Lajia1=2GEXa92srQ2s9wH--MrRHj+kSTtQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sat, 2019-12-14 at 22:44 +0100, Arnd Bergmann wrote:
> On Sat, Dec 14, 2019 at 12:27 PM Hans Verkuil <hverkuil@xs4all
> .nl> wrote:
> > 
> > On 12/13/19 4:32 PM, Hans Verkuil wrote:
> > > > > ...
> > > > 
> > > > I've heard good things about the prebuilt toolchains
> > > > from http://musl.cc/.
> > > > These seems to come with a libstdc++, but I have not
> > > > tried that myself.
> > > 
> > > I'll see if I can give those a spin, but if I can't get it
> > > to work quickly,
> > > then I don't plan on spending much time on it.
> > 
> > I managed to build v4l2-ctl/compliance with those
> > toolchains, but they seem to be
> > still using a 32-bit time_t.
> > 
> > Do I need to get a specific version or do something special?
> 
> My mistake: only musl-1.2.0 and up have 64-bit time_t, but
> this isn't released yet. According to https://wiki.musl-
> libc.org/roadmap.html, the release was planned for last month,
> no idea how long it will take.
> 
> It appears that a snapshot build at
> http://more.musl.cc/7.5.0/x86_64-linux-musl/i686-linux-musl-
> native.tgz is new enough to have 64-bit time_t (according to
> include/bits/alltypes.h), but this is a month old as well, so
> it may have known bugs.
> 
> Adding Zach to Cc here, maybe he already has plans for another
> build with the latest version.

Yes, that's correct. The current (as of 2019-12-19) GCC 9.2.1
offering is based on musl 1.1.24, though the 7.5.0 release is
using a more recent git tag only due to timing/availability.

Within reason, I'm happy to bump versions with justification.
Rebuilding takes about a full day but no time on my end.

Rich sent out a message [1] just today suggesting there is still
some time64 work to be done, so once he pushes those patches
I'll build and release new toolchains for 9.2, 8.3, and 7.5.


ZV

[1]: https://www.openwall.com/lists/musl/2019/12/19/6