All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Jay Carlson <nop@nop.com>
Cc: Hartvig Ekner <hartvige@mips.com>, linux-mips@oss.sgi.com
Subject: Re: Setting up of GP in static, non-PIC version of glibc?
Date: Tue, 26 Feb 2002 12:55:32 +0100	[thread overview]
Message-ID: <20020226125532.B7497@dea.linux-mips.net> (raw)
In-Reply-To: <334839BA-2A77-11D6-AB38-0030658AB11E@nop.com>; from nop@nop.com on Tue, Feb 26, 2002 at 12:10:50AM -0500

On Tue, Feb 26, 2002 at 12:10:50AM -0500, Jay Carlson wrote:

> By default non-PIC code *does* use $gp due to the brain damage in gas; 
> gas defaults to -G 8 unless told otherwise (-KPIC implies -G0 so we 
> don't see this in PIC code.)  gcc won't know anything about this, of 
> course.
> 
> What I'm doing in SUBTARGET_ASM_SPEC is to write something like 
> "%{fno-pic: %{!G: -G0}}"--if we're not in PIC mode, pass -G0 to gas by 
> default.
> 
> Anyway, once that's straightened out, -G8 does appear to work the way 
> you'd expect, with the code that Hartvig pasted above---I had written a 
> byte-for-byte identical patch :-)

I agree on that one except that 64kB of small data no longer seem to be
sufficient for every common application in the world.  So I'd vote for a
more defensive choice of the -G value, that is 0.

  Ralf

  reply	other threads:[~2002-02-26 12:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25 15:16 Setting up of GP in static, non-PIC version of glibc? Hartvig Ekner
2002-02-25 16:34 ` Ralf Baechle
2002-02-25 18:31   ` Johannes Stezenbach
2002-02-25 18:39     ` Ralf Baechle
2002-02-25 19:21       ` Hartvig Ekner
2002-02-25 19:21         ` Hartvig Ekner
2002-02-25 20:23         ` Ralf Baechle
2002-02-25 19:32       ` Johannes Stezenbach
2002-02-25 20:39         ` Ralf Baechle
2002-02-26  5:10   ` Jay Carlson
2002-02-26 11:55     ` Ralf Baechle [this message]
2002-02-26 14:55       ` Jay Carlson
2002-02-26 17:22         ` Ralf Baechle
2002-02-27 17:56           ` Hartvig Ekner

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=20020226125532.B7497@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=hartvige@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=nop@nop.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.