Am 15.05.2015 um 08:59 schrieb Peter Crosthwaite:
> On Sun, May 10, 2015 at 11:29 PM, Peter Crosthwaite
> wrote:
>> The helper function namespace is going to be tricky. I haven't tackled the
>> problem just yet, but looking for ideas on how we can avoid prefacing all
>> helpers with arch prefixes
Am 15.05.2015 um 08:47 schrieb Peter Crosthwaite:
> On Mon, May 11, 2015 at 3:27 AM, Andreas Färber wrote:
>> Hi,
>>
>> Am 11.05.2015 um 08:29 schrieb Peter Crosthwaite:
>>> Microblaze translation needs a change pattern to allow conversion to 64-bit
>>> TARGET_LONG. Uses of TCGv need to be removed
On Sun, May 10, 2015 at 11:29 PM, Peter Crosthwaite
wrote:
> Hi All,
>
> This is target-multi, a system-mode build that can support multiple
> cpu-types. Patches 1-3 are the main infrastructure. The hard part
> is the per-target changes needed to get each arch into an includable
> state.
>
> Two a
On Mon, May 11, 2015 at 3:27 AM, Andreas Färber wrote:
> Hi,
>
> Am 11.05.2015 um 08:29 schrieb Peter Crosthwaite:
>> Microblaze translation needs a change pattern to allow conversion to 64-bit
>> TARGET_LONG. Uses of TCGv need to be removed and explicited to 32-bit.
>
> I did have a patchset doin
Am 11.05.2015 um 10:21 schrieb Peter Crosthwaite:
> On Mon, May 11, 2015 at 12:13 AM, Peter Maydell
> wrote:
>> On 11 May 2015 at 07:29, Peter Crosthwaite
>> wrote:
>>> The env as handle by common code now needs to architecture-agnostic. The
>>> MB and ARM envs are refactored to have CPU_COMMON
Hi,
Am 11.05.2015 um 08:29 schrieb Peter Crosthwaite:
> Microblaze translation needs a change pattern to allow conversion to 64-bit
> TARGET_LONG. Uses of TCGv need to be removed and explicited to 32-bit.
I did have a patchset doing exactly that for one of my microcontroller
targets but someone (
On 11 May 2015 at 09:21, Peter Crosthwaite wrote:
> On Mon, May 11, 2015 at 12:13 AM, Peter Maydell
> wrote:
>> Do you give each CPU its own codegen buffer? (I'm thinking that some
>> of this might also be more easily done once multithreadded-TCG is
>> complete, since that will properly split the
On Mon, May 11, 2015 at 12:13 AM, Peter Maydell
wrote:
> On 11 May 2015 at 07:29, Peter Crosthwaite wrote:
>> This is target-multi, a system-mode build that can support multiple
>> cpu-types. Patches 1-3 are the main infrastructure. The hard part
>> is the per-target changes needed to get each ar
On 11 May 2015 at 07:29, Peter Crosthwaite wrote:
> This is target-multi, a system-mode build that can support multiple
> cpu-types. Patches 1-3 are the main infrastructure. The hard part
> is the per-target changes needed to get each arch into an includable
> state.
Interesting. This is somethin
Hi All,
This is target-multi, a system-mode build that can support multiple
cpu-types. Patches 1-3 are the main infrastructure. The hard part
is the per-target changes needed to get each arch into an includable
state.
Two architectures are initially converted. Microblaze and ARM. Step
by step con
10 matches
Mail list logo
