Paolo Bonzini writes:
> On 19/03/19 11:18, Alex Bennée wrote:
>>
>> Richard Henderson writes:
>>
>>> On 3/18/19 12:46 PM, Peter Maydell wrote:
Hi; for the M-profile floating point work I'm going to need I think
three new TB flags (to control whether to generate the code to do
th
On 3/19/19 8:06 AM, Paolo Bonzini wrote:
>> Given how many guests use the cs_base I wonder if it's time we came up
>> with a better name for it: extra_tb_state, extra_state, moar_bits...
>
> Or make the flags 64-bits by moving cs_base into the upper 32-bits of
> flags... This way 32-bit hosts do
On 19/03/19 11:18, Alex Bennée wrote:
>
> Richard Henderson writes:
>
>> On 3/18/19 12:46 PM, Peter Maydell wrote:
>>> Hi; for the M-profile floating point work I'm going to need I think
>>> three new TB flags (to control whether to generate the code to do
>>> the various independent things the
On 3/19/19 4:20 AM, Peter Maydell wrote:
> Speaking of VECSTRIDE, in theory we should implement the v8A
> requirement that FPSCR.Len and .Stride are either RAZ/WI or
> cause the insns which use Len and Stride to UNDEF if they are
> set to non-zero. At the moment we just have the v7A behaviour
> of
On Mon, 18 Mar 2019 at 23:36, Richard Henderson
wrote:
>
> On 3/18/19 12:46 PM, Peter Maydell wrote:
> > Hi; for the M-profile floating point work I'm going to need I think
> > three new TB flags (to control whether to generate the code to do
> > the various independent things the pseudocode Execu
Richard Henderson writes:
> On 3/18/19 12:46 PM, Peter Maydell wrote:
>> Hi; for the M-profile floating point work I'm going to need I think
>> three new TB flags (to control whether to generate the code to do
>> the various independent things the pseudocode ExecuteFPCheck() function
>> does be
On 3/18/19 12:46 PM, Peter Maydell wrote:
> Hi; for the M-profile floating point work I'm going to need I think
> three new TB flags (to control whether to generate the code to do
> the various independent things the pseudocode ExecuteFPCheck() function
> does before executing any FP insn). Unfortu
Hi; for the M-profile floating point work I'm going to need I think
three new TB flags (to control whether to generate the code to do
the various independent things the pseudocode ExecuteFPCheck() function
does before executing any FP insn). Unfortunately we currently have
only 2 unused bits in the
