Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Greg Satz <satz@ayrnetworks.com>, linux-mips@oss.sgi.com
Subject: Re: SHN_MIPS_SCOMMON
Date: Sun, 22 Jul 2001 01:20:16 +0200	[thread overview]
Message-ID: <20010722012016.I25928@bacchus.dhis.org> (raw)
In-Reply-To: <20010721120302.A10173@lucon.org>; from hjl@lucon.org on Sat, Jul 21, 2001 at 12:03:02PM -0700

On Sat, Jul 21, 2001 at 12:03:02PM -0700, H . J . Lu wrote:

> > Actually for all code; we don't support GP optimization in any of our code
> > models.
> 
> Even for the user space code?

Yes.  GP optimization isn't comparible with SVR4 PIC code.  I don't see a
fundamental problem to get that to work but gcc refuses the use of -G with
PIC code.

What would limit the value of the GP optimization is that for alot of code
a single 64kb GP data segment is not large enough; the IRIX compiler and
Alpha binutils afaik support a multi-gp code model already.

> Do you have a testcase to show what should be the desired behavior? As I
> understand, the SHN_MIPS_SCOMMON section only appears in the relocatable
> files. You won't see it in
> executables nor DSOs. Are there any problems with SHN_MIPS_SCOMMON
> in .o files? Can we always pass `-G 0' to the assemebler for Linux.

It's already guanteed that we never use GP optimization.  The particular
case which was reported by the user was caused ld directly which defaults to
-G 8.  That's not an issue for userspace.

  Ralf

  reply	other threads:[~2001-07-21 23:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-20 22:15 SHN_MIPS_SCOMMON Greg Satz
2001-07-20 22:15 ` SHN_MIPS_SCOMMON Greg Satz
2001-07-21  1:30 ` SHN_MIPS_SCOMMON Ralf Baechle
2001-07-21  9:22   ` SHN_MIPS_SCOMMON Greg Satz
2001-07-21  9:22     ` SHN_MIPS_SCOMMON Greg Satz
2001-07-21 12:11     ` SHN_MIPS_SCOMMON Ralf Baechle
2001-07-21 17:41       ` SHN_MIPS_SCOMMON H . J . Lu
2001-07-21 18:12         ` SHN_MIPS_SCOMMON Greg Satz
2001-07-21 18:12           ` SHN_MIPS_SCOMMON Greg Satz
2001-07-21 18:13           ` SHN_MIPS_SCOMMON H . J . Lu
2001-07-21 18:56             ` SHN_MIPS_SCOMMON Ralf Baechle
2001-07-21 19:03               ` SHN_MIPS_SCOMMON H . J . Lu
2001-07-21 23:20                 ` Ralf Baechle [this message]
2001-07-21 18:55         ` SHN_MIPS_SCOMMON 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=20010722012016.I25928@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=hjl@lucon.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=satz@ayrnetworks.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