On Fri, Sep 7, 2012 at 2:18 PM, Aurelien Jarno aurel...@aurel32.net wrote:
On Sun, Sep 02, 2012 at 05:33:47PM +, Blue Swirl wrote:
Add an explicit CPUState parameter instead of relying on AREG0
and switch to AREG0 free mode.
Signed-off-by: Blue Swirl blauwir...@gmail.com
---
configure
On Sat, Sep 08, 2012 at 08:35:18AM +, Blue Swirl wrote:
On Fri, Sep 7, 2012 at 2:18 PM, Aurelien Jarno aurel...@aurel32.net wrote:
On Sun, Sep 02, 2012 at 05:33:47PM +, Blue Swirl wrote:
Add an explicit CPUState parameter instead of relying on AREG0
and switch to AREG0 free mode.
On Fri, Sep 07, 2012 at 04:18:41PM +0200, Aurelien Jarno wrote:
On Sun, Sep 02, 2012 at 05:33:47PM +, Blue Swirl wrote:
Add an explicit CPUState parameter instead of relying on AREG0
and switch to AREG0 free mode.
Signed-off-by: Blue Swirl blauwir...@gmail.com
---
configure
On Fri, Sep 07, 2012 at 04:40:03PM +0200, Edgar E. Iglesias wrote:
On Fri, Sep 07, 2012 at 04:18:41PM +0200, Aurelien Jarno wrote:
On Sun, Sep 02, 2012 at 05:33:47PM +, Blue Swirl wrote:
Add an explicit CPUState parameter instead of relying on AREG0
and switch to AREG0 free mode.
case 6:
Similarly to what I reported for the microblaze and sh4 target, I think
we should not start using cpu_single_env (a global variable) to replace
env (a global variable stored in a register).
It is possible to pass env through the subroutine, though
Add an explicit CPUState parameter instead of relying on AREG0
and switch to AREG0 free mode.
Signed-off-by: Blue Swirl blauwir...@gmail.com
---
configure |2 +-
target-cris/Makefile.objs |2 -
target-cris/helper.c|4 +-
target-cris/helper.h| 34
