linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Neil Russell <caret@c-side.com>
To: Jacques.Menu@epfl.ch
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Linux/PPC assembly language documentation ?
Date: Thu, 16 Nov 2000 11:04:52 -0800	[thread overview]
Message-ID: <20001116110452.B31662@lx.c-side.com> (raw)
In-Reply-To: <200011161356.HAA11163@lists.linuxppc.org>; from Jacques MENU on Thu, Nov 16, 2000 at 02:56:18PM +0100


@l gives the lower 16-bits of the constant.
@h gives the upper 16-bits.
@ha gives the upper 16-bits adjusted so that carry from the lower 16-bits
    gives the correct result.

So, an example of correct use is:

	lis	r3, const@h
	ori	r3, r3, const@l

or

	lis	r3, const@ha
	addi	r3, r3, const@l

or

	lis	r3, addr@ha
	lbz	r4, addr@l(r3)

("lis rx, c" is "addis rx, rx, c").


Neil.



On Thu, Nov 16, 2000 at 02:56:18PM +0100, Jacques MENU wrote:
> I'm doing work on GNU Prolog that features a ppc_linux.c file, generating code the way shown below.
>
> I'd like to find a description of ''@ha' and '@l' used in instructions like  :
> 	addis	9,0,.Lcont001@ha
> and
> 	addi		9,9,.Lcont003@l
>
> Please answer by email too since I'm not yet a member of this list. Thanks a lot !
>
> Regards,
>
> ____________________
>
> void
> Pl_Call(char *label)
> {
> #ifndef MAP_REG_CP
>   Inst_Printf("addis", "9,0,.Lcont%d@ha", w_label);
>   Inst_Printf("addi", "9,9,.Lcont%d@l", w_label);
>   Inst_Printf("stw", "9,%s", asm_reg_cp);
> #else
>   Inst_Printf("addis", "%s,0,.Lcont%d@ha", asm_reg_cp, w_label);
>   Inst_Printf("addi", "%s,%s,.Lcont%d@l", asm_reg_cp, asm_reg_cp, w_label);
> #endif
>
>   Pl_Jump(label);
>   Label_Printf(".Lcont%d:", w_label++);
>
> #ifndef MAP_REG_E
>   if (use_envir)
>     Inst_Printf("lwz", "%s,%d(%s)", asm_reg_e, MAP_OFFSET_E, asm_reg_bank);
> #endif
> }
>
> --
> Dr Jacques MENU
> CUI - Université de Genève
>
> Tel:	++ 41 21 693 45 87
> mailto:Jacques.Menu@cui.unige.ch
> http://cui.unige.ch/~menu/1804
>

--
Neil Russell <caret@c-side.com>

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-11-16 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-16 13:56 Linux/PPC assembly language documentation ? Jacques MENU
2000-11-16 19:04 ` Neil Russell [this message]

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=20001116110452.B31662@lx.c-side.com \
    --to=caret@c-side.com \
    --cc=Jacques.Menu@epfl.ch \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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 NNTP newsgroup(s).