public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: rth@redhat.com (Richard Henderson)
Cc: gcc@gcc.gnu.org
Subject: Re: Help! DW function pointer encoding for PA
Date: Thu, 21 Feb 2002 11:33:00 -0000	[thread overview]
Message-ID: <200202211826.g1LIQZg1021937@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20020221002010.C18952@redhat.com> from "Richard Henderson" at Feb 21, 2002 00:20:10 am

> Note CODE==1 vs CODE==2.  You should be able to distinguish your
> two cases based on this.  If absolutely necessary, pass type information

That's in fact what I was trying to use.

> from ASM_PREFERRED_EH_DATA_FORMAT to ASM_MAYBE_OUTPUT_ENCODED_ADDR_RTX
> via bits >= 0x100, ie bits that won't appear in the output file.
> 
> Note that ia64 has the same sort of function descriptor vs FDE
> code label sorts of issues.

I'll have to look more carefully at the ia64.  I think I see what
ia64_expand_call is doing to handle the function descriptor vs FDE
issue:

      dest = force_reg (DImode, gen_rtx_MEM (DImode, addr));
      emit_move_insn (pic_offset_table_rtx,
		      gen_rtx_MEM (DImode, plus_constant (addr, 8)));

So, it explicitly loads the pic_offset_table_rtx.  I think we can do
the same.  I beginning to think indirect calls from one shared library
to another may never have worked on the PA.

Thanks,
Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

  reply	other threads:[~2002-02-21 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 23:48 John David Anglin
2002-02-21  0:52 ` Richard Henderson
2002-02-21 11:33   ` John David Anglin [this message]
     [not found] <no.id>
2002-02-21 13:31 ` John David Anglin
2002-02-21 19:28   ` David Edelsohn

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=200202211826.g1LIQZg1021937@hiauly1.hia.nrc.ca \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.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).