public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: binutils@sourceware.org
Subject: Re: News MIPS option -mno-shared
Date: Thu, 09 Dec 2004 18:19:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58L.0412091756310.18083@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <20041209153403.5294.qmail@gossamer.airs.com>

On Thu, 9 Dec 2004, Ian Lance Taylor wrote:

> The idea is that you can use -KPIC -mno-shared and get code which
> still uses the usual Unix calling convention, but is slightly more
> efficient at each function entry.  Of course, the resulting code is
> not position independent and can not be put into a shared library.

 The resulting naming of options is a bit unfortunate -- -KPIC suggests 
the result is PIC regardless of other options.

> Hence the name -mno-shared.  (Note that nothing will prevent you from
> trying to put -mno-shared code into a shared library, but the
> resulting shared library will not work correctly.)

 Shouldn't the relocations be forwarded to the .rel.dyn section upon
static linking for resolution (or complaint) by ld.so?  Like it happens
for other platforms where you can build PDC shared libraries that still
work.  Not that such libraries are optimal, but still better than ones
that silently break.

  Maciej

  parent reply	other threads:[~2004-12-09 18:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09 15:34 Ian Lance Taylor
2004-12-09 16:41 ` Richard Sandiford
2004-12-09 16:44   ` Ian Lance Taylor
2004-12-10  9:34     ` Richard Sandiford
2004-12-11  3:45       ` Ian Lance Taylor
2004-12-09 16:53 ` Thiemo Seufer
2004-12-09 18:03 ` David Daney
2004-12-09 20:32   ` Ian Lance Taylor
2004-12-10 13:45     ` Dave Korn
2004-12-10 14:12       ` Thiemo Seufer
2004-12-09 18:19 ` Maciej W. Rozycki [this message]
2004-12-09 21:05   ` Ian Lance Taylor
2004-12-09 18:52 ` David Daney
2004-12-09 21:20   ` Ian Lance Taylor
2005-02-21 22:42 ` David Daney

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=Pine.LNX.4.58L.0412091756310.18083@blysk.ds.pg.gda.pl \
    --to=macro@linux-mips.org \
    --cc=binutils@sourceware.org \
    --cc=ian@wasabisystems.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).