public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: binutils@sources.redhat.com
Subject: common assembly code between ppc32 & ppc64
Date: Tue, 20 Sep 2005 21:03:00 -0000	[thread overview]
Message-ID: <930FB6D0-944A-486B-A060-C63D4FC7E141@freescale.com> (raw)

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

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-20 21:03 Kumar Gala [this message]
2005-09-20 22:29 ` Andreas Schwab
2005-09-20 22:57   ` Kumar Gala
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=930FB6D0-944A-486B-A060-C63D4FC7E141@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    /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).