My patch is kind of trivial quick fix that just eliminates these unaligned
reads and doesn't seem to require complicated testing supposing my code
properly handles integer promotion (and hope it will not slow the
interpreter down).
Aligning everything, on the other hand, can not only remove the UB
> -原始邮件-
> 发件人: "Paolo Bonzini"
> 发送时间: 2018-01-25 17:59:03 (星期四)
> 收件人: linzhecheng , qemu-devel@nongnu.org
> 抄送: crosthwaite.pe...@gmail.com, r...@twiddle.net
> 主题: Re: [Qemu-devel] [PATCH] vcpu: create vcpu thread with
> QEMU_THREAD_DETACHED mode
>
> On 20/01/2018 08:54, linzhechen
Am 27.01.2018 um 14:49 schrieb Anatoly Trosinenko:
> Use ldl_he_p / ldq_he_p functions instead of a plain memory access
> through pointer.
>
> Signed-off-by: Anatoly Trosinenko
> ---
> tcg/tci.c | 16 +++-
> 1 file changed, 11 insertions(+), 5 deletions(-)
A better alternative might
Use ldl_he_p / ldq_he_p functions instead of a plain memory access
through pointer.
Signed-off-by: Anatoly Trosinenko
---
tcg/tci.c | 16 +++-
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/tcg/tci.c b/tcg/tci.c
index 33edca1903..410817cf6a 100644
--- a/tcg/tci.c
+++
The code in tcg/tci.c reads some data from TCI bytecode through
pointer dereferencing. As far as I know unaligned reads in such a way are
undefined behavior and compiling with -fsanitize=undefined enumerated
them as such at run-time.
I have replaced such reads with invocations of ld{l,q}_he_p.
A c
I am seeing this on my system as well - the exact same symptoms. Has
anyone investigated this problem?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1703795
Title:
Unable to release mouse in SDL2
Hi Philipppe,
On 25.01.2018 12:22, Philippe Mathieu-Daudé wrote:
> Hi Richard, Helge,
>
> On 01/24/2018 08:26 PM, Richard Henderson wrote:
>> From: Helge Deller
>>
>> Now that we have the prerequisites in target/hppa/,
>> implement the hardware for a PA7100LC.
>>
>> This also enables build for h
On Fri, Jan 26, 2018 at 11:25:24PM +0100, Greg Kurz wrote:
> In various place we don't correctly check if the device supports MSI or
> MSI-X. This can cause devices to be advertised with MSI support, even
> if they only support MSI-X (like virtio-pci-* devices for example):
>
> eth
