All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Miles Bader <miles@gnu.org>
Cc: Greg Ungerer <gerg@snapgear.com>,
	Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
	linux-kernel@vger.kernel.org
Subject: Re: common RODATA in vmlinux.lds.h (2.5.59)
Date: Wed, 22 Jan 2003 06:42:30 +0100	[thread overview]
Message-ID: <20030122054230.GA954@mars.ravnborg.org> (raw)
In-Reply-To: <buoptqp954l.fsf@mcspd15.ucom.lsi.nec.co.jp>

On Wed, Jan 22, 2003 at 01:32:10PM +0900, Miles Bader wrote:
> 
> [To be honest, I think the stuff with `LOAD_OFFSET' is a bit of a waste;
> it seems cleaner to just have archs define their own sections as
> appropriate, and use RODATA_CONTENTS directly -- it's the input sections
> and related symbols that are always changing (and so better centralized),
> after all, not the output sections.]

There were some reports of failed boots that boiled down to
mis-alignment of a single section.
With your suggestion we will end up in the same problem.
__start_ksymbtab will in some cases have a value less than the actual
start of the first symbol.

	Sam

  parent reply	other threads:[~2003-01-22  5:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22  2:05 common RODATA in vmlinux.lds.h (2.5.59) Greg Ungerer
2003-01-22  2:49 ` Kai Germaschewski
2003-01-22  3:25   ` Greg Ungerer
2003-01-22  4:32     ` Miles Bader
2003-01-22  4:47       ` Greg Ungerer
2003-01-22  5:42       ` Sam Ravnborg [this message]
2003-01-22  6:00         ` Miles Bader
2003-01-22  5:55       ` Kai Germaschewski
2003-01-22  6:23         ` Miles Bader
2003-01-22 16:32           ` Kai Germaschewski
2003-01-23  2:03             ` Miles Bader
2003-01-23  5:59             ` Greg Ungerer
2003-01-22  6:35         ` Greg Ungerer
2003-01-22 16:35           ` Kai Germaschewski

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=20030122054230.GA954@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=gerg@snapgear.com \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.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 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.