public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: Andreas Schwab <schwab@suse.de>
Cc: "Alan Modra" <amodra@bigpond.net.au>, <binutils@sources.redhat.com>
Subject: Re: common assembly code between ppc32 & ppc64
Date: Tue, 20 Sep 2005 22:57:00 -0000	[thread overview]
Message-ID: <CDA06E04-6027-42BB-8930-0AAF4837DFA5@freescale.com> (raw)
In-Reply-To: <jey85re8he.fsf@sykes.suse.de>

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."
>

  reply	other threads:[~2005-09-20 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-20 21:03 Kumar Gala
2005-09-20 22:29 ` Andreas Schwab
2005-09-20 22:57   ` Kumar Gala [this message]
2005-09-20 23:59     ` Andreas Schwab
2005-09-21  3:49       ` Kumar Gala

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CDA06E04-6027-42BB-8930-0AAF4837DFA5@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=schwab@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).