All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>, Pavel Machek <pavel@ucw.cz>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	tglx@linutronix.de, mingo@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.26-rc1 on x86: ld: warning: dot moved backwards before `.text'
Date: Sat, 10 May 2008 23:16:02 +0200	[thread overview]
Message-ID: <20080510211602.GA32339@uranus.ravnborg.org> (raw)
In-Reply-To: <482604D1.7020804@zytor.com>

On Sat, May 10, 2008 at 01:25:53PM -0700, H. Peter Anvin wrote:
> Mikael Pettersson wrote:
> >
> >The resulting kernel hasn't broken on me yet, however.
> >
> >A search through the LKML archives showed that this was reported
> >for 2.6.25-rc3-mm1, but I couldn't find any discussion about it
> >after that:
> >
> ><http://marc.info/?l=linux-kernel&m=120470303728010&w=2>
> >
> >The .config causing this warning is available in
> ><http://user.it.uu.se/~mikpe/linux/ale/config-2.6.26-rc1>
> >
> 
> This is because the organization of the file was changed, and the linker 
> script wasn't changed to match:
> 
> SECTIONS
> {
>         . = HEADER_OFFSET;
>         .header : {
>                  *(.header)
>         }
> 
>         . = 0;
>         .text : {
>                  *(.text*)
>         }
> 
> This is crap; the sections should be listed *in order* so the linker can 
> warn properly when something bad happens.
> 
> The code should be correct; reorganizing the linker script correctly 
> should fix the problem.

I need Pavel to comment on this.
Why we start with . equal 0x3f00 and then later as . equals 0x0000
I dunno.
I did not look into this part of the code back then - but I should anyway
have seen this flaw in the linker script :-(

	Sam

  parent reply	other threads:[~2008-05-10 21:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-10 20:18 2.6.26-rc1 on x86: ld: warning: dot moved backwards before `.text' Mikael Pettersson
2008-05-10 20:23 ` Rafael J. Wysocki
2008-05-10 20:25 ` H. Peter Anvin
2008-05-10 20:56   ` Rafael J. Wysocki
2008-05-11 18:52     ` Pavel Machek
2008-05-10 21:16   ` Sam Ravnborg [this message]
2008-05-11 15:44     ` Cyrill Gorcunov
2008-05-11 18:15       ` H. Peter Anvin
2008-05-11 18:24         ` Cyrill Gorcunov
2008-05-11 18:25           ` H. Peter Anvin
2008-05-11 18:29             ` Cyrill Gorcunov
2008-05-11 21:22               ` Rafael J. Wysocki
2008-05-12  4:15                 ` Cyrill Gorcunov
2008-05-12  6:16                   ` Cyrill Gorcunov
2008-05-12  6:52                 ` Pavel Machek
2008-05-11 18:54       ` Pavel Machek

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=20080510211602.GA32339@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=mingo@redhat.com \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    /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.