Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: jsoe0708@tiscali.be, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] warning: minor abi change
Date: Sat, 5 Jul 2003 22:12:10 -0600	[thread overview]
Message-ID: <20030706041210.GA16894@dsl2.external.hp.com> (raw)
In-Reply-To: <200307052353.h65NrZF4025169@hiauly1.hia.nrc.ca>

On Sat, Jul 05, 2003 at 07:53:34PM -0400, John David Anglin wrote:
> Instead of adding (void *) to each comparison,

This is just a temporary workaround and I have no plans of committing
any (void *) casts to fix this problem.

> you could add a kernel
> version of __canonicalize_funcptr_for_compare:
> 
> __canonicalize_funcptr_for_compare:
> 	bv %r0(%r2)
> 	copy %r26,%r28
> 
> or for PA 2.0
> 
> __canonicalize_funcptr_for_compare:
>         bve (%r2)
> 	copy %r26,%r28
> 
> I think there was a possible solution along these lines posted on the list
> a few months ago (joel?).

Ok.  I didn't see it when trolling the mail archive.
No matter, I'll try it.
Anyone have an opinion on which arch/parisc file this should go in?

> This solution assumes that canonicalization is unnecessary in the kernel.
> Probably, in most cases it is.  However, if you really need to canonicalize
> a function pointer from user space, then you are going to have to figure
> out how to call into the dynamic loader from the kernel.  This obviously
> isn't very safe.  So, possibly this implies that function pointers passed
> in syscalls should be canonicalized before the kernel is entered (i.e.,
> glibc should do the canonicalization).
> 
> As far as kernel modules go, I don't know how function pointers are
> handled.  If you pass a function pointer from one module to another,
> does it need canonicalization?

I depend on willy/tausq/amodra/et al to understand stuff like this.

> If canonicalization is never necessary
> in the kernel, possibly I could add a GCC option to disable canonicalization.

I think willy suggested privately that might be case.

> Sorry, about the lack of documentation.  To see what the function does,
> it's currently necessary to look in the GCC gcc/config/pa directory.

oh no problem. Kernel has lots of stale/missing documentation too.
Just need guidance on where to find the relevant code and which
path to take.

thanks,
grant

  reply	other threads:[~2003-07-06  4:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030627151546.GA30607@dsl2.external.hp.com>
     [not found] ` <3ED70CF10000AE2E@ocpmta2.freegates.net>
2003-06-27 16:54   ` [parisc-linux] warning: minor abi change Grant Grundler
2003-06-28 10:48     ` Joel Soete
2003-07-05 23:08   ` Grant Grundler
2003-07-05 23:53     ` John David Anglin
2003-07-06  4:12       ` Grant Grundler [this message]
2003-07-06 16:12         ` Joel Soete
2003-07-07 20:02         ` Carlos O'Donell
2003-07-07 20:19           ` John David Anglin
2003-07-08  1:45             ` Carlos O'Donell
2003-07-06  5:57     ` [parisc-linux] IDE modules build prob Grant Grundler
2003-07-06  6:31       ` Grant Grundler
2003-07-06  7:23         ` Alan Cox
     [not found] <20030711065156.GA17025@dsl2.external.hp.com>
2003-07-11  8:26 ` [parisc-linux] warning: minor abi change Joel Soete
2003-07-11 10:24   ` Alan Cox
2003-06-26 13:54 Matthew Wilcox
2003-06-26 17:03 ` Joel Soete
2003-06-26 17:06   ` Matthew Wilcox
2003-06-26 17:45     ` Randolph Chung
2003-06-27 14:41     ` Joel Soete
2003-06-27 16:21     ` Joel Soete
2003-06-27 16:52       ` Alan Cox
2003-07-07 16:00         ` Joel Soete
2003-07-07 16:05           ` Alan Cox
2003-07-07 16:31             ` Matthew Wilcox
2003-07-07 16:39               ` Joel Soete
2003-07-07 16:33             ` Joel Soete

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=20030706041210.GA16894@dsl2.external.hp.com \
    --to=grundler@parisc-linux.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=jsoe0708@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.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