Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@convergence.de>
To: Ralf Baechle <ralf@oss.sgi.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: Mon, 25 Feb 2002 19:31:41 +0100	[thread overview]
Message-ID: <20020225183141.GA3560@convergence.de> (raw)
In-Reply-To: <20020225173433.B3680@dea.linux-mips.net>

On Mon, Feb 25, 2002 at 05:34:33PM +0100, Ralf Baechle wrote:
> On Mon, Feb 25, 2002 at 04:16:20PM +0100, Hartvig Ekner wrote:
> 
> >         .globl ENTRY_POINT
> >         .type ENTRY_POINT,@function
> > ENTRY_POINT:
> > #ifdef __PIC__
> >         SET_GP
> > #else
> >         la  $28, _gp
> > #endif
> > 
> > Makes things work (this code ends in crt1.o). Is this the right place to 
> > fix it?
> 
> Non-PIC code doesn't use $gp, so any reference to $gp is a bug.  Note
> that we don't support global data optimization for ELF either that is,
> -G 0 is the default.

I recently experimented with dietlibc and tried to create
static, non-PIC binaries, with some success.
Contradicting the docs (gcc info), -G 0 is not the default but
has to be passed explicitely (even when using the GNU assembler).

BTW: Who is "we"? Do you mean global data optimization is broken
in gcc/binutils or just that no one at SGI is using it?


Regards,
Johannes

  reply	other threads:[~2002-02-25 19:31 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 [this message]
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
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=20020225183141.GA3560@convergence.de \
    --to=js@convergence.de \
    --cc=hartvige@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@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