This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: In the NONSTOP implementation why dose gdb use register r0 and r1 as temp registers for rn and rd ?

From: xingxing pan <forandom at gmail dot com>
To: gdb at sourceware dot org
Date: Mon, 3 May 2010 22:16:37 +0800
Subject: Re: In the NONSTOP implementation why dose gdb use register r0 and r1 as temp registers for rn and rd ?
References: <n2s77f815bd1005022227tc4c6422cj35ca8fd96df840f1@mail.gmail.com>

Can anyone help?

2010/5/3 xingxing pan <forandom@gmail.com>:
> hey guys, I'm porting NONSTOP to an ARM similar architechure. I found
> the following comments in the source.
>
> Instruction is of form:
> <op><cond> rd, [rn,] #imm
> Rewrite as:
> Preparation:
> tmp1, tmp2 <- r0,r1
> r0,r1 <- rd,rn
> Insn: <op><cond> r0,r1 #imm
> Cleanup: rd <- r0; r0<-tmp1;r1<-tmp2
>
> why dose gdb use register r0 and r1? why not use rd and rn directly?
> Thank you!
>

References:
- In the NONSTOP implementation why dose gdb use register r0 and r1 as temp registers for rn and rd ?
  - From: xingxing pan

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]