From: David Huggins-Daines <dhd@linuxcare.com>
To: law@cygnus.com
Cc: Alan Modra <amodra@linuxcare.com.au>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Non-bootable kernel problems
Date: 14 Jul 2000 14:53:23 -0400 [thread overview]
Message-ID: <87aefkzgpo.fsf@linuxcare.com> (raw)
In-Reply-To: Jeffrey A Law's message of "Fri, 14 Jul 2000 10:39:22 -0600"
Jeffrey A Law <law@cygnus.com> writes:
> Either we need to avoid merging the section symbols to avoid twiddling
> the addend, or we need to avoid reducing relocs to section symbols to
> begin with.
We only reduce relocations to section symbols for static data. It
seems that every other platform I've investigated (Sparc, PowerPC,
Alpha) does the same thing, so, while I think it would be possible to
not reduce them on PA, I'm not sure what the unintended side effects
would be.
As for not merging section symbols ... I'm not sure how that would be
done, but if it's the only option I guess we can figure it out.
Alan: any thoughts on this?
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
next prev parent reply other threads:[~2000-07-14 18:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 23:35 [parisc-linux] Non-bootable kernel problems Richard Hirst
2000-07-13 17:14 ` Paul Bame
2000-07-13 18:46 ` David Huggins-Daines
2000-07-13 21:14 ` David Huggins-Daines
2000-07-13 19:20 ` Jeffrey A Law
2000-07-14 16:10 ` David Huggins-Daines
2000-07-14 16:39 ` Jeffrey A Law
2000-07-14 18:53 ` David Huggins-Daines [this message]
2000-07-14 20:40 ` David Huggins-Daines
2000-07-14 22:14 ` GAS fix for reloc problems (was Re: [parisc-linux] Non-bootable kernel problems) David Huggins-Daines
2000-07-15 8:33 ` Alan Modra
2000-07-15 1:31 ` [parisc-linux] Non-bootable kernel problems Alan Modra
2000-07-13 23:45 ` David Huggins-Daines
2000-07-14 0:44 ` Alan Modra
2000-07-14 16:02 ` Jeffrey A Law
2000-07-14 16:02 ` David Huggins-Daines
2000-07-14 16:37 ` Jeffrey A Law
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=87aefkzgpo.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=amodra@linuxcare.com.au \
--cc=law@cygnus.com \
--cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.