public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jack Carter <Jack.Carter@imgtec.com>
Cc: "libc-ports@sourceware.org" <libc-ports@sourceware.org>
Subject: Re: [RFC][PATCH] MIPS ifunc for glibc
Date: Sun, 18 Aug 2013 20:39:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1308182031510.10353@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4CEFBC1BE64A8048869F799EF2D2EEEE01AAE1FA@BADAG02.ba.imgtec.org>

On Sat, 17 Aug 2013, Jack Carter wrote:

> This is the initial MIPS ifunc patch for glibc. This patch should be
> applied in conjunction with the binutils patch.

Do you have an ABI document specifying all the relevant semantics, for all 
three ABIs?

Why aren't you consistently passing the HWCAP value to resolver functions 
(it seems some places pass it but others don't)?  If you don't pass it 
from the start, it could be problematic to change the ABI later to start 
passing it, as applications' IFUNC resolvers wouldn't know if they are 
being run with a glibc version that passes the HWCAP value to them or not.  
The ABI document should presumably specify what arguments get passed to 
the resolver function....

> +    case R_MIPS_IRELATIVE:
> +      {
> +	ElfW(Addr) value;
> +
> +	/* The address for the got entry storing the address for the */
> +	/* ifunc routine is in this relocation. To get the address of */
> +	/* the function to use on this machine the ifunc routine is run */
> +	/* and its return value is the address which is then put back */
> +	/* into the got entry. */

Ordinary multi-line comment, please.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2013-08-18 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-17  0:31 Jack Carter
2013-08-18 20:39 ` Joseph S. Myers [this message]
2013-08-20  0:38   ` Jack Carter
2013-08-20 14:03     ` Joseph S. Myers

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=Pine.LNX.4.64.1308182031510.10353@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=Jack.Carter@imgtec.com \
    --cc=libc-ports@sourceware.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).