From: Segher Boessenkool <segher@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>, paulus@samba.org
Subject: Re: [POWERPC] iSeries: supress lparmap.c warning
Date: Mon, 18 Dec 2006 11:41:08 +0100 [thread overview]
Message-ID: <AAD83AF0-5271-47AA-B278-E96A4E691F74@kernel.crashing.org> (raw)
In-Reply-To: <20061218161429.4ffeec4e.sfr@canb.auug.org.au>
> lparmap.c: Assembler messages:
> lparmap.c:43: Warning: ignoring changed section attributes for .text
>
> We do not need the .section ops in the generated .s file, so
> just remove them.
Nasty stuff.
const struct LparMap __attribute__((__section__(".text"))) xLparMap = {
This will declare the .text section as non-executable. Whoops.
Another way around this, which is perhaps a bit hacky but
doesn't require your post-processing, is to use
__section__(".text #")
which will cut off the compiler-generated "a" (where the assembler
wants "ax", which is the default) :-)
Segher
prev parent reply other threads:[~2006-12-18 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 5:14 [POWERPC] iSeries: supress lparmap.c warning Stephen Rothwell
2006-12-18 10:41 ` Segher Boessenkool [this message]
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=AAD83AF0-5271-47AA-B278-E96A4E691F74@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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