public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: V R <mipsdev18@gmail.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: how to generate - "procedure linkage table" for MIPS
Date: Thu, 05 Apr 2018 00:05:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1804042352080.1545@tp.orcam.me.uk> (raw)
In-Reply-To: <CAGdV6F-b-wqNQV2JYhq5_RTBG1m=sFAE8tJOWiy-d_F4qMDV_Q@mail.gmail.com>

Hi Vidya,

On Mon, 5 Mar 2018, V R wrote:

> Also on enabling gcc on MIPS with "–with-mips-plt " option the plt stub
> wasnt seen. Is there
> 
> anything missing that needs to be done or is there any limitation , please
> let me know.

 What problem are you trying to solve?  Can you run `readelf -S' on a MIPS 
executable you think you have a trouble with and post the result?

 NB MIPS shared libraries use the so called lazy binding stubs, where the 
call is always indirect, rather than a procedure linkage table to achieve 
a similar effect, so you won't ever see a PLT in a MIPS shared library.

  Maciej

      reply	other threads:[~2018-04-04 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05  9:23 V R
2018-04-05  0:05 ` Maciej W. Rozycki [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=alpine.DEB.2.00.1804042352080.1545@tp.orcam.me.uk \
    --to=macro@mips.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mipsdev18@gmail.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).