Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Joel Soete <soete.joel@tiscali.be>
Cc: Matthew Wilcox <willy@debian.org>, parisc-linux@parisc-linux.org
Subject: RE: [parisc-linux] init and exit text problem
Date: 16 Jan 2004 12:30:17 -0500	[thread overview]
Message-ID: <1074274218.2443.12.camel@mulgrave> (raw)
In-Reply-To: <4004805D000027C1@ocpmta3.freegates.net>

On Fri, 2004-01-16 at 11:50, Joel Soete wrote:
> +  /* When something in the kernel is NOT compiled as a module, the
> +   * module cleanup code and data are put into these segments.  Both
> +   * can then be thrown away, as cleanup code is never called unless
> +   * it's a module.
> +   */
> +  /DISCARD/ : {
> +	*(.exit.text)
> +	*(.exit.data)

This is wrong...exit.text and exit.data are runtime discards, not link
time ones, precisely because of the compile failures you get.

> +	*(.exitcall.exit)

This one should be OK.

I'm not sure we can actually do this, though...I seem to remember that
our 64 bit toolchain is not too happy doing discard sections.

James

  parent reply	other threads:[~2004-01-16 17:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15  0:18 [parisc-linux] init and exit text problem Matthew Wilcox
2004-01-16 16:50 ` Joel Soete
2004-01-16 16:58   ` Joel Soete
2004-01-16 17:30   ` James Bottomley [this message]
2004-01-16 20:14     ` Randolph Chung
2004-01-16 18:47       ` James Bottomley
2004-01-17  0:12         ` James Bottomley
2004-01-17  8:17           ` Grant Grundler
2004-01-19 11:16             ` Joel Soete
2004-01-19 18:57               ` Grant Grundler
  -- strict thread matches above, loose matches on Subject: below --
2004-01-20 18:12 Joel Soete

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=1074274218.2443.12.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=parisc-linux@parisc-linux.org \
    --cc=soete.joel@tiscali.be \
    --cc=willy@debian.org \
    /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