Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Re: gcj can't make shared libs on hppa
Date: Sun, 12 Mar 2006 22:12:47 +0800	[thread overview]
Message-ID: <44142C5F.3040509@tausq.org> (raw)
In-Reply-To: <200603120210.k2C2AvIw012101@hiauly1.hia.nrc.ca>

> r22 should be pointing to a function descriptor and have the plabel
> bit set.  It's a relative rare situation when an indirect call can
> be made directly (no shared libraries).

I know, but that's not what's happening....

__do_global_ctors_aux() looks like this:

static void __attribute__((used))
__do_global_ctors_aux (void)
{
   func_ptr *p;
   for (p = __CTOR_END__ - 1; *p != (func_ptr) -1; p--)
     (*p) ();
}

what i'm seeing is that we are calling the copy of this function in 
liba1.so, and loading __CTOR_END__ via the GOT, but we are using an r19 
value that is pointing inside libgcj.so, so we end up loading some wrong 
value for __CTOR_END__

I don't know how/why this is happening though. how does this bit work? 
each .so has its own copy of __do_global_ctors_aux(); how does this get 
called and where does it setup r19 for each .so before this gets called?

randolph
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

       reply	other threads:[~2006-03-12 14:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603120210.k2C2AvIw012101@hiauly1.hia.nrc.ca>
2006-03-12 14:12 ` Randolph Chung [this message]
2006-03-12 15:10   ` [parisc-linux] Re: gcj can't make shared libs on hppa John David Anglin
2006-03-12 15:27     ` John David Anglin
2006-03-12 15:56       ` John David Anglin
     [not found] <17433.20663.776171.375034@gargle.gargle.HOWL>
2006-03-17 18:00 ` John David Anglin
     [not found] <no.id>
2006-03-12 20:15 ` John David Anglin
2006-03-13 14:24   ` Carlos O'Donell
2006-03-13 20:50     ` John David Anglin
     [not found] <4412FACA.2010102@tausq.org>
2006-03-12  2:10 ` John David Anglin
     [not found] <200602220005.k1M05o1D006305@hiauly1.hia.nrc.ca>
2006-03-11 16:28 ` Randolph Chung
     [not found] <200602212135.k1LLZiUn005694@hiauly1.hia.nrc.ca>
2006-02-22  0:05 ` John David Anglin
     [not found] <17402.31286.940841.655257@gargle.gargle.HOWL>
2006-02-21 21:35 ` John David Anglin
2006-03-14  0:39 ` John David Anglin
2006-02-21  2:25 Matthias Klose

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=44142C5F.3040509@tausq.org \
    --to=randolph@tausq.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --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