On 28/4/26 11:33, Peter Maydell wrote:
From: CJ Chen <[email protected]>
When it comes to this pattern: .valid.unaligned = false and
impl.unaligned = true, is effectlvely contradictory. The .valid
structure indicates that unaligned access should be rejected at
the access validation phase, yet .impl suggests the underlying
device implementation can handle unaligned operations. As a result,
the upper-layer code will never even reach the .impl logic.
Add an assertion that the MemoryRegionOps doesn't specify
this invalid combination.
Signed-off-by: CJ Chen <[email protected]>
Tested-by: CJ Chen <[email protected]>
Suggested-by: Peter Xu <[email protected]>
Acked-by: Tomoyuki Hirose <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
[PMM: tweaked commit message]
Reviewed-by: Peter Maydell <[email protected]>
Signed-off-by: Peter Maydell <[email protected]>
---
system/memory.c | 1 +
1 file changed, 1 insertion(+)
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
