Question about address resolving code (64bit)

--===============0002434052559427800==
Content-Type: multipart/alternative; boundary="0000000000007044bd0587556676"

--0000000000007044bd0587556676
Content-Type: text/plain; charset="UTF-8"

Hello everyone,

I'm working on a project which involves X86 emulation, and it's going great
so far (Bochs is a really good source to learn from).
I've been studying parts of the code but there's a thing that doesn't make
sense to me.
In BxResolve64 (cpu/cpu.h), why doesn't it do "& i->asize_mask()" like
BxResolve32 does?
Surely you'd still need to cut off high bytes depending on the address-size
prefix, right?

Thank you.

--0000000000007044bd0587556676
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Hello everyone,<div><br>=
</div><div>I&#39;m working on a project which involves X86 emulation, and i=
t&#39;s going great so far (Bochs is a really good source to learn from).</=
div><div>I&#39;ve been studying parts of the code but there&#39;s a thing t=
hat doesn&#39;t make sense to me.</div><div>In BxResolve64 (cpu/cpu.h), why=
 doesn&#39;t it do &quot;&amp; i-&gt;asize_mask()&quot; like BxResolve32 do=
es?</div><div>Surely you&#39;d still need to cut off high bytes depending o=
n the address-size prefix, right?</div><div><br></div><div>Thank you.</div>=
</div></div></div>

--0000000000007044bd0587556676--


--===============0002434052559427800==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============0002434052559427800==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
bochs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bochs-developers

--===============0002434052559427800==--