From: ralf@uni-koblenz.de
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: Emacs problem
Date: Fri, 28 Aug 1998 12:31:54 +0200 [thread overview]
Message-ID: <19980828123154.B358@uni-koblenz.de> (raw)
In-Reply-To: <19980825225603.43888@alpha.franken.de>; from Thomas Bogendoerfer on Tue, Aug 25, 1998 at 10:56:03PM +0200
On Tue, Aug 25, 1998 at 10:56:03PM +0200, Thomas Bogendoerfer wrote:
> Another questione does gcc/egcs produce .sdata, .lit4 or .li8 sections
> on Linux/MIPS ?
These sections are mostly being used for code using global pointer
optimization. .lit8 is also being used for fp code when assembling li.d
macros.
For kernel code global pointer optimization is incompatible
with our current use of $gp as the current pointer; in userland gp
optimization is incompatible with PIC code.
Ralf
next prev parent reply other threads:[~1998-08-28 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-23 20:36 Emacs problem Thomas Bogendoerfer
1998-08-24 10:19 ` ralf
1998-08-25 20:56 ` Thomas Bogendoerfer
1998-08-28 10:31 ` ralf [this message]
1998-08-29 0:08 ` Thomas Bogendoerfer
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=19980828123154.B358@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.com \
--cc=tsbogend@alpha.franken.de \
/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