From: "H. J. Lu" <hjl@lucon.org>
To: Eric Christopher <echristo@redhat.com>
Cc: linux-mips@oss.sgi.com,
GNU C Library <libc-alpha@sources.redhat.com>,
binutils@sources.redhat.com
Subject: Re: MIPS GOT overflow in gcc 3.2.
Date: Mon, 1 Jul 2002 23:58:49 -0700 [thread overview]
Message-ID: <20020701235849.A6382@lucon.org> (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
On Mon, Jul 01, 2002 at 08:09:59PM -0700, Eric Christopher wrote:
>
> > AFAIK it happens to mozilla as well.
> >
> > Guh.
>
> There are a few different possible solutions, one is to do the
> -fPIC/-fpic split, another is to copy to SGI multigot, I'm sure there
> are other solutions as well...
>
I am testing this patch now. It will take a day to verify it.
H.J.
----
2002-07-02 H.J. Lu <hjl@gnu.org>
* ltcf-gcj.sh (ac_cv_prog_cc_pic): Add "-Wa,-xgot" for
Linux/mips.
--- ltcf-gcj.sh.xgot Mon Sep 10 08:39:17 2001
+++ ltcf-gcj.sh Mon Jul 1 23:49:06 2002
@@ -639,6 +639,14 @@ fi
ac_cv_prog_cc_pic=-Kconform_pic
fi
;;
+ linux*)
+ ac_cv_prog_cc_pic='-fPIC'
+ case $host_cpu in
+ mips*)
+ ac_cv_prog_cc_pic="$ac_cv_prog_cc_pic -Wa,-xgot"
+ ;;
+ esac
+ ;;
*)
ac_cv_prog_cc_pic='-fPIC'
;;
next prev parent reply other threads:[~2002-07-02 6:55 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 [this message]
2002-07-02 18:48 ` Greg Lindahl
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=20020701235849.A6382@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=libc-alpha@sources.redhat.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