• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 2555 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How interpret the asm lines

Vincent R
Note: This was originally posted on 1st December 2009 at http://forums.arm.com

Hi,

I am trying to understand how a library compiled for arm is working and I have a problem to undertstand the following lines :
You just need to know that GDGStackRef and GDGStateRef  are pointers to structure and that GDStack is defined like that :

typedef struct __GDGStack {

signed long refcount; //0x00
long capacity;   //0x04
size_t index;   //0x08
GDGStateRef *gstate; //0x0C

} GDGStack, *GDGStackRef;



GDGStackRef GDGStackCreateWithGState(GDGStateRef stateSrc)
{
GDGStackRef stack;
GDGStateRef gstateTemp;

__text:000025EE                 MOV     R6, R0

... Some code not interesting ...

__text:0000261E ; ---------------------------------------------------------------------------
__text:0000261E
__text:0000261E loc_261E                                ;
__text:0000261E                 CBNZ    R6, loc_2626         ; if (stateSrc) goto loc_2626
__text:00002620                 BL      _GDGStateCreate ; gstateTemp = GDGStateCreate();
__text:00002624                 B       loc_262C ; goto loc_262C;
__text:00002626 ; ---------------------------------------------------------------------------

... Some code not interesting ...

__text:0000262C loc_262C                               
__text:0000262C                 MOV     R5, R0  ; R5 = gstateTemp;
__text:0000262E                 CBNZ    R0, loc_263A ; if (gstateTemp) goto loc_263A

... Some code not interesting ...


__text:0000263A
__text:0000263A loc_263A                                ;
__text:0000263A                 LDR     R3, [R4,#8] ;          R3 = stack->index
__text:0000263C                 LDR     R2, [R4,#0xC] ;  R2 = stack->gstate
__text:0000263E                 STR.W   R0, [R2,R3,LSL#2];
__text:00002642                 ADDS    R3, #1  ;
__text:00002644                 STR     R3, [R4,#8] ;  stack->index++


My problem is to understand R0, [R2,R3,LSL#2], how would you interpret ?
Could you detailed ?
Parents
  • Note: This was originally posted on 2nd December 2009 at http://forums.arm.com

    STR.W R0, [R2,R3,LSL#2];

    Stores R0 to the address in R2, plus the value in R3 logically-shifted-left by 2;
    i.e. it's implementing something like:

      stack->gstate[stack->index] = gstateTemp;

    The shift-left by two is equivalent to mutiply by four, which is the sizeof int.
    It converts an index into a byte offset for an array made up of four byte elements.

    hth
    s.


    Thanks that's what I thought but I find it weird that compiler produces that kind of sequence because in this case
    it knows that index is 0.
    So it would be better to produce something like :

    STR.W R0, [R2];
Reply
  • Note: This was originally posted on 2nd December 2009 at http://forums.arm.com

    STR.W R0, [R2,R3,LSL#2];

    Stores R0 to the address in R2, plus the value in R3 logically-shifted-left by 2;
    i.e. it's implementing something like:

      stack->gstate[stack->index] = gstateTemp;

    The shift-left by two is equivalent to mutiply by four, which is the sizeof int.
    It converts an index into a byte offset for an array made up of four byte elements.

    hth
    s.


    Thanks that's what I thought but I find it weird that compiler produces that kind of sequence because in this case
    it knows that index is 0.
    So it would be better to produce something like :

    STR.W R0, [R2];
Children
No data