linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sean MacLennan <smaclennan@pikatech.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: warning: allocated section `.data_nosave'  not in segment
Date: Mon, 28 Sep 2009 11:53:16 -0400	[thread overview]
Message-ID: <20090928115316.7e0b7db9@lappy.seanm.ca> (raw)
In-Reply-To: <20090928013654.466c9b72@opus.seanm.ca>

I looked into it some more.... the patch converts this section:

        . = ALIGN(PAGE_SIZE);
        .data_nosave : AT(ADDR(.data_nosave) - LOAD_OFFSET) {
               __nosave_begin = .;
               *(.data.nosave)
               . = ALIGN(PAGE_SIZE);
               __nosave_end = .;
        }

to:

	.data_nosave : AT(ADDR(.data_nosave) - LOAD_OFFSET) {
		NOSAVE_DATA
	}

If you expand the NOSAVE_DATA macro, you get:

	.data_nosave : AT(ADDR(.data_nosave) - LOAD_OFFSET) {
		. = ALIGN(PAGE_SIZE);
		VMLINUX_SYMBOL(__nosave_begin) = .;
		*(.data.nosave)
		. = ALIGN(PAGE_SIZE);
		VMLINUX_SYMBOL(__nosave_end) = .;
	}

If you ignore the VMLINUX_SYMBOL, the only difference is moving the
ALIGN inside the brackets. If I move the ALIGN back where it was, then
the warning goes away.

But other sections moved the ALIGN without an issue. Could it be a
compiler problem? We are using  version 4.0.0 (DENX ELDK 4.1 4.0.0).

Cheers,
   Sean

  reply	other threads:[~2009-09-28 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-25 20:54 warning: allocated section `.data_nosave' not in segment Sean MacLennan
2009-09-28  5:36 ` Sean MacLennan
2009-09-28 15:53   ` Sean MacLennan [this message]
2009-09-28 20:56     ` Segher Boessenkool
2009-09-28 23:24       ` Sean MacLennan
2009-09-29  0:29         ` Segher Boessenkool

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=20090928115316.7e0b7db9@lappy.seanm.ca \
    --to=smaclennan@pikatech.com \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).