From: Daniel Jacobowitz <drow@false.org>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: David Daney <ddaney@avtrex.com>, binutils@sources.redhat.com
Subject: Re: RFC: Patch to fix MIPS -mno-shared with multi-got...
Date: Fri, 04 Mar 2005 00:41:00 -0000 [thread overview]
Message-ID: <20050304004114.GA9623@nevyn.them.org> (raw)
In-Reply-To: <20050303232729.GP1272@rembrandt.csv.ica.uni-stuttgart.de>
On Fri, Mar 04, 2005 at 12:27:29AM +0100, Thiemo Seufer wrote:
> David Daney wrote:
> > But it is possible to have C code like this:
> >
> > extern int _gp;
> >
> >
> > int
> > foo()
> > {
> > int *bar = &_gp;
> > /* Do something with the primary GOT */
> > }
> >
> > In this case the existing semantics are clear. It is the primary GOT.
>
> Whithout having looked it up, I doubt the ABI gives the program any
> guarantee about the contents of the GOT.
I know at least one dynamic linker that works this way. Of course, it
uses the symbol _GLOBAL_OFFSET_TABLE_ for consistency with other
platforms, so it won't be directly affected; but there may be others.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-04 0:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 21:05 David Daney
2005-03-03 21:48 ` Richard Sandiford
2005-03-03 22:34 ` David Daney
2005-03-03 22:49 ` Thiemo Seufer
2005-03-03 23:15 ` David Daney
2005-03-03 23:27 ` Thiemo Seufer
2005-03-04 0:41 ` Daniel Jacobowitz [this message]
2005-03-03 23:57 ` David Daney
2005-03-04 0:43 ` Daniel Jacobowitz
2005-03-04 9:36 ` Richard Sandiford
2005-03-04 19:43 ` New " David Daney
2005-03-04 19:45 ` Daniel Jacobowitz
2005-03-04 21:53 ` David Daney
2005-03-04 22:12 ` Thiemo Seufer
2005-03-04 22:21 ` David Daney
2005-03-04 23:40 ` Eric Christopher
2005-03-05 0:03 ` Thiemo Seufer
2005-03-04 4:31 ` RFC: " Ian Lance Taylor
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=20050304004114.GA9623@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=ddaney@avtrex.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
/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).