From: Suprateeka R Hegde <hegdesmailbox@gmail.com>
To: Carlos O'Donell <carlos@redhat.com>,
Roland McGrath <roland@hack.frob.com>
Cc: gnu-gabi@sourceware.org
Subject: Re: Deferred Binding of Function Pointers in SHLIB
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <b444005c-8650-d7f5-1e99-7c6cafecc648@gmail.com> (raw)
In-Reply-To: <fe2baeb4-440c-09e3-810c-32ac14e777b4@redhat.com>
On 14-Jun-2016 02:33 AM, Carlos O'Donell wrote:
> On 06/13/2016 11:27 AM, Suprateeka R Hegde wrote:
>> I have an executable with hundreds of function pointers as an array.
>> Functions are called using array index which depends on the arguments
>> passed to the executable. This executable is short lived and in each
>> invocation calls only one function.
>
> Could you please provide a small code example that shows the exact
> problem?
Its already there. The examples I have given are also exact problems.
The shlib behavior and exe behavior are different.
--
Supra
prev parent reply other threads:[~2016-06-18 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 Suprateeka R Hegde
2016-01-01 0:00 ` Roland McGrath
2016-01-01 0:00 ` Suprateeka R Hegde
2016-01-01 0:00 ` Carlos O'Donell
2016-01-01 0:00 ` Suprateeka R Hegde [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=b444005c-8650-d7f5-1e99-7c6cafecc648@gmail.com \
--to=hegdesmailbox@gmail.com \
--cc=carlos@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=roland@hack.frob.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).