From: Greg Lindahl <lindahl@keyresearch.com>
To: linux-mips@oss.sgi.com
Subject: Re: MIPS GOT overflow in gcc 3.2.
Date: Tue, 2 Jul 2002 11:48:43 -0700 [thread overview]
Message-ID: <20020702114843.B1896@wumpus.internal.keyresearch.com> (raw)
In-Reply-To: <1025579401.1785.0.camel@ghostwheel.cygnus.com>; from echristo@redhat.com on Mon, Jul 01, 2002 at 08:09:59PM -0700
> 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.
greg
next prev parent reply other threads:[~2002-07-02 18:47 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 [this message]
2002-07-02 18:55 ` H. J. Lu
2002-07-02 18:58 ` Daniel Jacobowitz
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=20020702114843.B1896@wumpus.internal.keyresearch.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox