common assembly code between ppc32 & ppc64

common assembly code between ppc32 & ppc64

[Kumar Gala]

Alan,

I was wondering if there was any GNU asm magic that you where aware  
of to deal with the fact that pointers are different sizes on ppc32  
vs ppc64.  For example:

#ifndef __powerpc64__
#define END_FTR_SECTION(msk, val)               \
99:                                             \
         .section __ftr_fixup,"a";               \
         .align 2;                               \
         .long msk;                              \
         .long val;                              \
         .long 98b;                              \
         .long 99b;                              \
         .previous
#else /* __powerpc64__ */
#define END_FTR_SECTION(msk, val)               \
99:                                             \
         .section __ftr_fixup,"a";               \
         .align 3;                               \
         .llong msk;                             \
         .llong val;                             \
         .llong 98b;                             \
         .llong 99b;                             \
         .previous
#endif /* __powerpc64__ */


Is there any magic to handle ".llong" vs ".long" that we could  
possibly use to reduce the duplication between these two code fragments.

thanks

- kumar

Re: common assembly code between ppc32 & ppc64

[Andreas Schwab]

Kumar Gala <kumar.gala@freescale.com> writes:

> Is there any magic to handle ".llong" vs ".long" that we could  
> possibly use to reduce the duplication between these two code fragments.

#ifndef __powerpc64__
        .macro pointer val
        .long \val
        .endm
        .macro align_p
        .align 2
        .endm
#else
        .macro pointer val
        .llong \val
        .endm
        .macro align_p
        .align 3
        .endm
#endif

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: common assembly code between ppc32 & ppc64

[Kumar Gala]

Andreas,

Can you explain further what this gets me ?

I kinda get the align_p macro portion, but I'm not sure I understand  
the 'pointer' and \val stuff.

thanks

- kumar

On Sep 20, 2005, at 4:26 PM, Andreas Schwab wrote:

> Kumar Gala <kumar.gala@freescale.com> writes:
>
>
>> Is there any magic to handle ".llong" vs ".long" that we could
>> possibly use to reduce the duplication between these two code  
>> fragments.
>>
>
> #ifndef __powerpc64__
>         .macro pointer val
>         .long \val
>         .endm
>         .macro align_p
>         .align 2
>         .endm
> #else
>         .macro pointer val
>         .llong \val
>         .endm
>         .macro align_p
>         .align 3
>         .endm
> #endif
>
> Andreas.
>
> -- 
> Andreas Schwab, SuSE Labs, schwab@suse.de
> SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
> Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>

Re: common assembly code between ppc32 & ppc64

[Andreas Schwab]

Kumar Gala <kumar.gala@freescale.com> writes:

> I kinda get the align_p macro portion, but I'm not sure I understand  
> the 'pointer' and \val stuff.

Read about the macro directive in the GAS manual.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: common assembly code between ppc32 & ppc64

[Kumar Gala]

Thanks, learn something new everyday :)

- kumar

On Sep 20, 2005, at 5:29 PM, Andreas Schwab wrote:

> Kumar Gala <kumar.gala@freescale.com> writes:
>
>
>> I kinda get the align_p macro portion, but I'm not sure I understand
>> the 'pointer' and \val stuff.
>>
>
> Read about the macro directive in the GAS manual.
>
> Andreas.
>
> -- 
> Andreas Schwab, SuSE Labs, schwab@suse.de
> SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
> Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>