public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: law@cygnus.com
Cc: pooh@msu.net, Michael Meissner <meissner@cygnus.com>, egcs@cygnus.com
Subject: Re: libgcc problems
Date: Thu, 15 Jan 1998 16:30:00 -0000	[thread overview]
Message-ID: <9801151707.AA23404@rios1.watson.ibm.com> (raw)
In-Reply-To: <10216.884832018@hurl.cygnus.com>

>>>>> Jeffrey A Law writes:

>> Understand. Uphh! After long debugging I found a problem! This is because
>> in current exception handling implementation __sjthrow() code can not
>> be in shared library. Otherwise, no operation to restore original TOC
>> anchor pointer is performed.

Jeff> Sounds like the rs6000.md needs a nonlocal_goto_receiver pattern to
Jeff> restore the TOC.

	rs6000.md does have a nonlocal_goto_receiver pattern added by
Meissner, but it only handles the GCC minimal-toc case where GCC has
allocated a secondary TOC register.  The code assumes that the system TOC
is correct in order to access the secondary TOC anchor value.  It looks
like all nonlocal patterns for AIX assume that all of the functions are
within the same module.

	The SVR4 case only seems to handle a secondary GOT.  How does SVR4
handle this normally?  It looks like one needs to materialize a copy of
the original TOC anchor.

David

  parent reply	other threads:[~1998-01-15 16:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5010300014296319000002L092*@MHS>
1998-01-15 16:30 ` pooh
1998-01-14 18:38   ` Jeffrey A Law
1998-01-15 16:06     ` Andrey Slepuhin
1998-01-15 16:30     ` David Edelsohn [this message]
1998-01-15 16:30       ` Jeffrey A Law
1998-01-16  1:51         ` David Edelsohn
1998-01-17 22:30       ` Richard Henderson
1998-01-16  1:51     ` David Edelsohn
1998-01-15 16:30       ` Andrey Slepuhin
1998-01-16 20:09         ` David Edelsohn
1998-01-15 16:30 ` pooh
1998-01-15 16:30   ` David Edelsohn
1998-01-15 16:30     ` Andrey Slepuhin
1998-01-16 20:09 Andrey Slepuhin
1998-01-17 23:02 ` David Edelsohn
1998-01-19  2:30   ` Andrey Slepuhin
1998-01-19  8:19     ` David Edelsohn
1998-01-19 15:31       ` Andrey Slepuhin
1998-01-19 15:31         ` David Edelsohn
1998-01-20  4:00           ` Andrey Slepuhin
1998-01-20  4:00             ` David Edelsohn
1998-01-20  2:21 Mike Stump
1998-01-19 15:31 ` Andrey Slepuhin
1998-01-20  5:48 Andrey Slepuhin
1998-01-20  9:45 ` 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=9801151707.AA23404@rios1.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    --cc=meissner@cygnus.com \
    --cc=pooh@msu.net \
    /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).