From: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
To: binutils@sourceware.org
Subject: Re: Omit output section from executable
Date: Wed, 02 Aug 2006 21:20:00 -0000 [thread overview]
Message-ID: <20060802232018.211498e4@laptop.hypervisor.org> (raw)
In-Reply-To: <20060802205019.GA30722@nevyn.them.org>
On Wed, 2 Aug 2006 16:50:19 -0400 Daniel Jacobowitz (DJ) wrote:
DJ> I'm not sure exactly what you want, but if the data is useless, try
DJ> making the .cpulocal section "nobits".
Nobits is what I want indeed. In assembler sources I can do:
.section .cpulocal, "aw", @nobits
foo: .long
and I get
.cpulocal 00000004 00000000 00000000 000000ba 2**0
ALLOC
But how can I achieve the same for C sources? When I write:
unsigned foo __attribute__((section (".cpulocal")));
I get
.cpulocal 00000004 00000000 00000000 00000034 2**2
CONTENTS, ALLOC, LOAD, DATA
Thanks,
- Udo
next prev parent reply other threads:[~2006-08-02 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 20:43 Udo A. Steinberg
2006-08-02 20:50 ` Daniel Jacobowitz
2006-08-02 21:20 ` Udo A. Steinberg [this message]
2006-08-02 21:29 ` Daniel Jacobowitz
2006-08-03 0:44 ` Alan Modra
2006-08-03 1:02 ` Udo A. Steinberg
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=20060802232018.211498e4@laptop.hypervisor.org \
--to=us15@os.inf.tu-dresden.de \
--cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).