public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
	linux-arch@vger.kernel.org,
	Parisc List <linux-parisc@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Sam Ravnborg <sam@ravnborg.org>, Tim Abbott <tabbott@ksplice.com>,
	Tim Bird <tim.bird@am.sony.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Matt Fleming <matt@console-pimps.org>,
	Arnd Bergmann <arnd@arndb.de>, Anders Kaseorg <andersk@mit.edu>,
	Andi Kleen <andi@firstfloor.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 2/4] module linker script: coalesce function and data sections
Date: Tue, 03 Aug 2010 15:47:26 +0200	[thread overview]
Message-ID: <4C581DEE.8080205@suse.cz> (raw)
In-Reply-To: <1280360876-2571-3-git-send-email-vda.linux@googlemail.com>

On 29.7.2010 01:47, Denys Vlasenko wrote:
>  SECTIONS {
> +
> +	/* Coalesce sections produced by gcc -ffunction-sections */
> +	.text   0 : AT(0) { *(.text .text.[A-Za-z0-9_$^]*) }
> +
> +	/* Coalesce sections produced by gcc -fdata-sections */
> +	.rodata 0 : AT(0) { *(.rodata .rodata.[A-Za-z0-9_$^]*) }
> +	.data   0 : AT(0) { *(.data .data.[A-Za-z0-9_$^]*) }
> +	.bss    0 : AT(0) { *(.bss .bss.[A-Za-z0-9_$^]*) }
> +
>  	/DISCARD/ : { *(.discard) }
>  }

I'm now getting

ld:/home/mmarek/linux-2.6/scripts/module-common.lds:23: ignoring invalid
character `^' in script
ld:/home/mmarek/linux-2.6/scripts/module-common.lds:26: ignoring invalid
character `^' in script
ld:/home/mmarek/linux-2.6/scripts/module-common.lds:27: ignoring invalid
character `^' in script
ld:/home/mmarek/linux-2.6/scripts/module-common.lds:28: ignoring invalid
character `^' in script

when linking modules and a similar warning when linking vmlinux (caused
by the next patch in series). I tried writing the carets as \^, but that
doesn't help at all...

$ ld --version
GNU ld (GNU Binutils; openSUSE Factory) 2.20.0.20100122-7

Michal

  parent reply	other threads:[~2010-08-03 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 23:47 [PATCH 0/4] function/data-sections Denys Vlasenko
2010-07-28 23:47 ` [PATCH 1/4] modpost: support objects with more than 64k sections Denys Vlasenko
2010-07-28 23:47 ` [PATCH 2/4] module linker script: coalesce function and data sections Denys Vlasenko
2010-07-29  0:25   ` David Howells
2010-07-29  1:24     ` Denys Vlasenko
2010-07-29  9:09       ` David Howells
2010-08-03 13:47   ` Michal Marek [this message]
2010-08-06  2:18     ` Denys Vlasenko
2010-07-28 23:47 ` [PATCH 3/4] kernel linker stripts: accomodate " Denys Vlasenko
2010-07-28 23:47 ` [PATCH 4/4] boot " Denys Vlasenko

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=4C581DEE.8080205@suse.cz \
    --to=mmarek@suse.cz \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=andersk@mit.edu \
    --cc=andi@firstfloor.org \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=sam@ravnborg.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tabbott@ksplice.com \
    --cc=tim.bird@am.sony.com \
    --cc=vda.linux@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox