From: Daniel Jacobowitz <dan@debian.org>
To: "H. J. Lu" <hjl@lucon.org>
Cc: Greg Lindahl <lindahl@keyresearch.com>, linux-mips@oss.sgi.com
Subject: Re: MIPS GOT overflow in gcc 3.2.
Date: Tue, 2 Jul 2002 14:58:03 -0400 [thread overview]
Message-ID: <20020702185803.GA6785@nevyn.them.org> (raw)
In-Reply-To: <20020702115525.A16419@lucon.org>
On Tue, Jul 02, 2002 at 11:55:25AM -0700, H. J. Lu wrote:
> On Tue, Jul 02, 2002 at 11:48:43AM -0700, Greg Lindahl wrote:
> > > AFAIK it happens to mozilla as well.
> >
> > On AlphaLinux, we eventually acquired multigot. Many large apps were
> > tripping on this problem; many big C++ programs essentially use
> > whole-program compilation, and many HPC codes link a bazillion large
> > libraries. I don't understand if -fpic or -fPIC are as good of a
> > solution as multigot.
>
> FYI, it is -Wa,-xgot, not -fPIC. multigot may be better. But it is not
> supported on mips. Until someone adds it, it is not an option.
No, it's the difference between -fpic and -fPIC. Also not yet
implemented. I intend to implement multigot in a couple of months if
no one else bothers to first.
You can not link modules with different GOT models together last I
checked, HJ. That means that if any static code from libgcc is used in
libjava you'll lose badly with -Wa,-xgot. Ditto libc_nonshared.a.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-07-02 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020701184640.A2043@lucon.org>
2002-07-02 2:07 ` MIPS GOT overflow in gcc 3.2 Eric Christopher
2002-07-02 3:09 ` Eric Christopher
2002-07-02 6:58 ` H. J. Lu
2002-07-02 18:48 ` Greg Lindahl
2002-07-02 18:55 ` H. J. Lu
2002-07-02 18:58 ` Daniel Jacobowitz [this message]
2002-07-03 16:35 ` RFC: Use -Wa,-xgot for Linux/mips (Re: MIPS GOT overflow in gcc 3.2.) H. J. Lu
2002-07-03 16:40 ` Daniel Jacobowitz
2002-07-03 16:50 ` H. J. Lu
2002-07-03 23:02 ` Ralf Baechle
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=20020702185803.GA6785@nevyn.them.org \
--to=dan@debian.org \
--cc=hjl@lucon.org \
--cc=lindahl@keyresearch.com \
--cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.