From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Luc Van Oostenryck" <luc.vanoostenryck@gmail.com>,
linux-sparse@vger.kernel.org
Cc: Jeff Layton <jlayton@redhat.com>
Subject: Re: [ANNOUNCE] Sparse v0.6.4
Date: Wed, 29 Sep 2021 22:35:40 +0100 [thread overview]
Message-ID: <ff8b358e-fd8a-9fc3-2ed9-2a85b6872560@ramsayjones.plus.com> (raw)
In-Reply-To: <d1eadca6-2c2c-b4af-7c0a-e49698a17b12@kleine-koenig.org>
On 29/09/2021 07:54, Uwe Kleine-König wrote:
> Hello,
>
> On 9/29/21 12:43 AM, Ramsay Jones wrote:
>> On 28/09/2021 20:56, Uwe Kleine-König wrote:
>>> On 9/6/21 6:21 AM, Luc Van Oostenryck wrote:
>>>> Sparse v0.6.4 is now out.
>>>
>>> I finally came around to update the Debian packaging. There is just a (non-critical) problem on x32 where some tests fail. I didn't look deeply, but if you care, now you know :-)
>>>
>>> https://buildd.debian.org/status/fetch.php?pkg=sparse&arch=x32&ver=0.6.4-1&stamp=1632795062&raw=0
>>
>> Hmm, interesting. I tested on Linux Mint 19 32-bit and didn't see any
>> failures. As far as I can tell, only the 'validation/builtin-objsize0.c'
>> test is failing (squinting hard at the above!).
>
> Note that the "normal" 32-bit build was just fine[1]. It's "only" x32[2] that is affected.
Ah, I missed that small detail. :)
Thanks for putting me right (before booting up my 32-bit system).
ATB,
Ramsay Jones
prev parent reply other threads:[~2021-09-29 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 4:21 [ANNOUNCE] Sparse v0.6.4 Luc Van Oostenryck
2021-09-06 10:04 ` Ben Dooks
2021-09-07 6:29 ` Luc Van Oostenryck
2021-09-28 21:05 ` Ben Dooks
2021-09-28 19:56 ` Uwe Kleine-König
2021-09-28 22:43 ` Ramsay Jones
2021-09-29 6:54 ` Uwe Kleine-König
2021-09-29 21:35 ` Ramsay Jones [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=ff8b358e-fd8a-9fc3-2ed9-2a85b6872560@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=jlayton@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=uwe@kleine-koenig.org \
/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).