From: David Howells <dhowells@redhat.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: dhowells@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] frv: Remove duplicate output of .exit.data
Date: Sat, 13 Oct 2007 10:17:51 +0100 [thread overview]
Message-ID: <21428.1192267071@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0710121633480.21684@blysk.ds.pg.gda.pl>
Maciej W. Rozycki <macro@linux-mips.org> wrote:
> When CONFIG_DEBUG_INFO is unset the input .exit.data sections are copied
> twice to vmlinux. Remove the copy made to .init.text and keep one in
> .data only.
No, they aren't. I believe the linker only makes one copy of each section,
and once a copy is inserted, all other attempts to make a copy of it are
ignored.
NAK.
David
next prev parent reply other threads:[~2007-10-14 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 15:40 [PATCH] frv: Remove duplicate output of .exit.data Maciej W. Rozycki
2007-10-13 9:17 ` David Howells [this message]
2007-10-15 15:27 ` Maciej W. Rozycki
2007-10-15 20:43 ` David Howells
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=21428.1192267071@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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