public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Martin Schwidefsky" <schwidefsky@de.ibm.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: binutils@gcc.gnu.org
Subject: Re: Fix for s390_elf_cons.
Date: Tue, 31 Jul 2001 00:59:00 -0000	[thread overview]
Message-ID: <OF6B4FAFBD.68ECFC51-ONC1256A9A.002AE145@de.ibm.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]

>Somewhat :)  I'm claiming that the subtraction of the current location is
>implicit since you are using a pc-relative relocation.
>
>Consider an analogy with pcrel call insns on many architectures.  We
>write "call foo", which generates a pcrel reloc against foo with an
>implicit subtraction of ".".  We don't write "call foo - .".  On x86,
>which uses a pcrel plt reloc, we have "call foo@PLT" too, not
>"call foo@PLT - ."  This extends to ".long foo@PLT" if you want a
>pcrel plt reloc.

Yes in the case of a call instruction it makes sense. We make use of
the same notation for the brasl instruction in the 64 bit assembler.
It makes sense because the instructions gives you the hint that you
are dealing with an implicit "- .". In the case of .long you don't
have that hint. And a ".long printk@PLT + . - .LT0_0" is somewhat
harder to understand than ".long printk@PLT - .LT0_0". The pseudo
op .long is by itself absolute.

blue skies,
   Martin

Linux/390 Design & Development, IBM Deutschland Entwicklung GmbH
Schönaicherstr. 220, D-71032 Böblingen, Telefon: 49 - (0)7031 - 16-2247
E-Mail: schwidefsky@de.ibm.com


             reply	other threads:[~2001-07-31  0:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31  0:59 Martin Schwidefsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-13  0:59 Martin Schwidefsky
2001-07-30 11:43 Martin Schwidefsky
2001-07-30 18:19 ` Alan Modra
2001-07-29 14:58 Martin Schwidefsky
2001-07-29 16:55 ` H . J . Lu
2001-07-29 21:17 ` Alan Modra
2001-08-07  4:41 ` Andreas Jaeger
2001-08-07  5:59   ` Alan Modra
2001-08-07  6:04     ` Andreas Jaeger

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=OF6B4FAFBD.68ECFC51-ONC1256A9A.002AE145@de.ibm.com \
    --to=schwidefsky@de.ibm.com \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).