Il 18/08/2014 00:23, Peter Maydell ha scritto: > Um. I think in general colliding memory regions imply a bug in the > machine model which is creating them. We have the collisions > disabled because nobody's got round to fixing this bug in the > PC model yet and it happens to be harmless there. I'm not > really convinced that yanking out the check code is better than > fixing the PC model...
I'm not sure I can parse anything in the commit message for a5e1cbc80 (which disabled the warning). I guess I'll try to revert that one and see what happens. Paolo
