From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Pierrick Bouvier <pierrick.bouvier@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: contrib/plugins does not build on 32-bit host
Date: Mon, 16 Dec 2024 19:25:59 +0000 [thread overview]
Message-ID: <87cyhr1lbs.fsf@draig.linaro.org> (raw)
In-Reply-To: <03bf8242-8dd7-43ae-a0a5-3f304aa546bd@linaro.org> (Richard Henderson's message of "Fri, 13 Dec 2024 23:29:13 -0600")
Richard Henderson <richard.henderson@linaro.org> writes:
> On 12/13/24 21:44, Pierrick Bouvier wrote:
>> Hi Richard,
>> On 12/13/24 13:47, Richard Henderson wrote:
>>> Hi,
>>>
>>> Several of the recent contrib/plugins/ patches do not build on e.g. arm32.
>>> All of the issues are related to casting between pointers and uint64_t; there is a Werror
>>> generated for casting between pointers and integers of different sizes.
>>>
>>> I suspect all of the instances will need to use separate structures to store uint64_t
>>> within the hash tables. The hash values themselves can use uintptr_t, as "hash" by
>>> definition loses data.
>>>
>>> The following is *not* a suggested patch, just touches every place with an error to
>>> highlight all of the places.
>>>
>> This is something I already tried to fix this way, but alas, casting
>> values is not enough, we might lose information (in the case where
>> guest is 64 bits). Some plugins need a refactoring to allocate data
>> dynamically, instead of hiding it under a pointer.
>> See this previous series:
>> https://patchew.org/QEMU/20240814233645.944327-1-pierrick.bouvier@linaro.org/
>> Finally, we discussed it was not worth the effort, and Alex simply
>> deactivated plugins by default for 32 bits platform, so it should
>> not be built for arm 32 bits. If we really have someone that needs
>> this usecase, we might make the effort, but for now, it does not
>> seem worth the hassle.
>
> Hmm. I didn't delete my 32-bit build tree, but it certainly
> re-configured. If plugins are supposed to be disabled, something may
> be wrong there...
Something should have triggered re-running config.status and triggering
the disable. I wonder why that didn't work.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2024-12-16 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 21:47 contrib/plugins does not build on 32-bit host Richard Henderson
2024-12-14 3:44 ` Pierrick Bouvier
2024-12-14 5:29 ` Richard Henderson
2024-12-14 6:10 ` Pierrick Bouvier
2024-12-14 12:35 ` Philippe Mathieu-Daudé
2024-12-16 18:45 ` Pierrick Bouvier
2024-12-16 20:53 ` Pierrick Bouvier
2024-12-16 19:25 ` Alex Bennée [this message]
2024-12-17 1:11 ` Pierrick Bouvier
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=87cyhr1lbs.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.