Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Cary Coutant <cary@cup.hp.com>
To: <law@redhat.com>, "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: "Alan Modra" <alan@linuxcare.com.au>, <bame@fc.hp.com>,
	<parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] where to put 64 bit libmilli?
Date: Thu, 4 Jan 2001 11:00:49 -0800	[thread overview]
Message-ID: <200101041902.LAA22273@adlmail.cup.hp.com> (raw)

>For PA64 the indirect calling sequence is significantly simpler and is
>emitted inline, hence we don't need/use $$dyncall for PA64.

Even for PA-32, $$dyncall should be simple enough to emit inline. There 
were two reasons why we didn't do it at first:

1. Our compilers emitted code that was compatible with both MPE and 
HP-UX. Since function pointers had different representations in these two 
runtimes, $$dyncall had to check a low-order bit.

2. After we implemented shared libraries on HP-UX, function pointers 
could be either "internal" or "external", and $$dyncall had to check.

Eventually, HP-UX has moved to a runtime where function pointers are 
either all internal (for a statically-bound program) or all external (for 
a dynamically-bound program). We now have compiler options to generate 
the appropriate inline sequence for either model.

Linux shouldn't need to be concerned with either of these cases. If 
you're using $$dyncall for the 32-bit runtime, I strongly suggest that 
you change the compiler.

-cary

             reply	other threads:[~2001-01-04 18:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04 19:00 Cary Coutant [this message]
2001-01-04 19:15 ` [parisc-linux] where to put 64 bit libmilli? Grant Grundler
  -- strict thread matches above, loose matches on Subject: below --
2001-01-04 21:20 Cary Coutant
2001-01-02 19:25 Paul Bame
2001-01-02 19:39 ` John David Anglin
2001-01-02 19:58   ` Paul Bame
2001-01-02 20:17     ` Jeffrey A Law
2001-01-03  1:46       ` Alan Modra
2001-01-03  1:57         ` Matthew Wilcox
2001-01-03  2:34           ` Alan Modra
2001-01-03  3:37         ` Jeffrey A Law
2001-01-03  4:11           ` Alan Modra
2001-01-03  4:15             ` Jeffrey A Law
2001-01-03  4:44               ` Alan Modra
2001-01-04  4:04                 ` Jeffrey A Law
2001-01-04  5:20                   ` Alan Modra
2001-01-04  6:18                     ` John David Anglin
2001-01-04  7:03                       ` Alan Modra
2001-01-04 16:36                         ` Paul Bame
2001-01-04 17:06                           ` Jeffrey A Law
2001-01-04 17:29                       ` Jeffrey A Law
2001-01-04 17:37                     ` Jeffrey A Law
2001-01-04 17:41                       ` Paul Bame
2001-01-04 23:52                       ` Alan Modra

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=200101041902.LAA22273@adlmail.cup.hp.com \
    --to=cary@cup.hp.com \
    --cc=alan@linuxcare.com.au \
    --cc=bame@fc.hp.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=law@redhat.com \
    --cc=parisc-linux@thepuffingroup.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