Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: Ulrich Teichert <krypton@ulrich-teichert.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] kernel module relocation bug
Date: Mon, 29 Nov 2004 11:46:18 -0800	[thread overview]
Message-ID: <20041129194618.GM6359@tausq.org> (raw)
In-Reply-To: <200411291927.iATJRY3e032306@arbas.nms.ulrich-teichert.org>

> I've seen this quite often in userspace on hppa-linux, lately while building
> TAO (http://www.cs.wustl.edu/~schmidt/TAO.html).

what error do you see? the one that recommends rebuilding with
-ffunction-sections?

in your application, do you first build some .o's, link them together
into a bigger .o, and then use those to create your final application
image? (otherwise i don't think this problem should occur; if it does
there's a bug somewhere that we should fix).

> Wouldn't there a way to fix that somewhere else in the toolchain? Or is
> there a parisc machine code limitation in the way? I would really get rid of
> -ffunction-sections as it seems to generate slower executables. Could
> you please explain what needs to be done?

we have (or, rather, Dave has) been fixing this in various places. This
problem happens much less frequently now than it used to. Fixes may be
required either in gcc or in the linker to detect when a branch target
is too far away and needs to be converted to a long branch.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-11-29 19:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27  6:47 [parisc-linux] kernel module relocation bug Randolph Chung
2004-11-29 15:32 ` James Bottomley
2004-11-29 15:33 ` James Bottomley
2004-11-29 19:27   ` Ulrich Teichert
2004-11-29 19:46     ` Randolph Chung [this message]
2004-11-29 22:51       ` Ulrich Teichert
2004-11-29 23:46         ` John David Anglin
2004-12-02 21:54           ` [parisc-linux] Userland relocation problems resolved (was: kernel module relocation bug) Ulrich Teichert
2004-12-02 22:51             ` [parisc-linux] Re: Userland relocation problems resolved (was: kernel module relocat John David Anglin
2004-11-29 23:53 ` [parisc-linux] kernel module relocation bug John David Anglin
2004-11-29 23:54   ` Randolph Chung
2004-11-29 23:57   ` Randolph Chung
2004-11-30  0:08     ` John David Anglin
2004-11-30  0:11       ` James Bottomley
2004-11-30  0:23         ` John David Anglin
2004-11-30  1:18           ` James Bottomley

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=20041129194618.GM6359@tausq.org \
    --to=tausq@debian.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=krypton@ulrich-teichert.org \
    --cc=parisc-linux@lists.parisc-linux.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