Re: [RFC PATCH v3 31/34] Hexagon (target/hexagon) translation

2020-08-30 Thread Richard Henderson
On 8/30/20 12:37 PM, Taylor Simpson wrote: > I'm actually checking two conditions here. > 1) packet crossing a page boundary > 2) reading too many words without finding the end of the packet. > I guess it would be better to separate them. > > What is the correct behavior for the second case? Shou

RE: [RFC PATCH v3 31/34] Hexagon (target/hexagon) translation

2020-08-30 Thread Taylor Simpson
> -Original Message- > From: Richard Henderson > Sent: Friday, August 28, 2020 8:50 PM > To: Taylor Simpson ; qemu-devel@nongnu.org > Cc: phi...@redhat.com; laur...@vivier.eu; riku.voi...@iki.fi; > aleksandar.m.m...@gmail.com; a...@rev.ng > Subject: Re: [RFC PA

Re: [RFC PATCH v3 31/34] Hexagon (target/hexagon) translation

2020-08-28 Thread Richard Henderson
On 8/18/20 8:50 AM, Taylor Simpson wrote: > Read the instruction memory > Create a packet data structure > Generate TCG code for the start of the packet > Invoke the generate function for each instruction > Generate TCG code for the end of the packet > > Signed-off-by: Taylor Simpson > --- > tar

[RFC PATCH v3 31/34] Hexagon (target/hexagon) translation

2020-08-18 Thread Taylor Simpson
Read the instruction memory Create a packet data structure Generate TCG code for the start of the packet Invoke the generate function for each instruction Generate TCG code for the end of the packet Signed-off-by: Taylor Simpson --- target/hexagon/translate.h | 103 +++ target/hexagon/transl