From: Kai Tietz <ktietz70@googlemail.com>
To: Dave Korn <dave.korn.cygwin@gmail.com>, binutils@sourceware.org
Subject: Re: SEC_NEVER_LOAD cleanup
Date: Sat, 16 Oct 2010 20:08:00 -0000 [thread overview]
Message-ID: <AANLkTima-b18poWw=8RSP3-dT=2Vt2T4FhMd5oGH3OTr@mail.gmail.com> (raw)
In-Reply-To: <20101016023559.GB26553@bubble.grove.modra.org>
2010/10/16 Alan Modra <amodra@gmail.com>:
> On Fri, Oct 15, 2010 at 09:54:18PM +0100, Dave Korn wrote:
>> > .gnu_debuglink_overlay ALIGN(__section_alignment__) (NOLOAD):
>> > {
>> > BYTE(0) /* c */
>> > BYTE(0) /* y */
>> > BYTE(0) /* g */
>> > BYTE(0) /* w */
>> > BYTE(0) /* i */
>> > BYTE(0) /* n */
>> > BYTE(0) /* 1 */
>> > BYTE(0) /* . */
>> > BYTE(0) /* d */
>> > BYTE(0) /* b */
>> > BYTE(0) /* g */
>> > BYTE(0) /* \0 */
>> > LONG(0) /* checksum */
>> > }
>
> Using your script with a small tweak for ELF gave me the same error.
>
>> I think (haven't checked yet) that this looks like a consequence of the
>> ldlang.c changes. Any thoughts on how to fix it?
>
> Like this, I think, just as we discard input sections and padding in
> noload sections. Can you test this out for me on cygwin?
>
> * ldwrite.c (build_link_order <lang_data_statement_enum>): Don't
> output when section has no contents.
> (build_link_order <lang_reloc_statement_enum>): Likewise.
>
> Index: ld/ldwrite.c
> ===================================================================
> RCS file: /cvs/src/src/ld/ldwrite.c,v
> retrieving revision 1.32
> diff -u -p -r1.32 ldwrite.c
> --- ld/ldwrite.c 22 Sep 2010 14:20:24 -0000 1.32
> +++ ld/ldwrite.c 16 Oct 2010 01:26:37 -0000
> @@ -51,6 +51,11 @@ build_link_order (lang_statement_union_t
> output_section = statement->data_statement.output_section;
> ASSERT (output_section->owner == link_info.output_bfd);
>
> + if (!((output_section->flags & SEC_HAS_CONTENTS) != 0
> + || ((output_section->flags & SEC_LOAD) != 0
> + && (output_section->flags & SEC_THREAD_LOCAL))))
> + break;
> +
> link_order = bfd_new_link_order (link_info.output_bfd, output_section);
> if (link_order == NULL)
> einfo (_("%P%F: bfd_new_link_order failed\n"));
> @@ -191,6 +196,11 @@ build_link_order (lang_statement_union_t
> output_section = rs->output_section;
> ASSERT (output_section->owner == link_info.output_bfd);
>
> + if (!((output_section->flags & SEC_HAS_CONTENTS) != 0
> + || ((output_section->flags & SEC_LOAD) != 0
> + && (output_section->flags & SEC_THREAD_LOCAL))))
> + break;
> +
> link_order = bfd_new_link_order (link_info.output_bfd, output_section);
> if (link_order == NULL)
> einfo (_("%P%F: bfd_new_link_order failed\n"));
>
> --
> Alan Modra
> Australia Development Lab, IBM
>
Well, this looks ok, too. But AFAICS it is touching just the surface.
My recent patch took care that for PE-COFF the content of the
debugging sections didn't got zero'ed. Maybe it is a general failure
to assume (at least for pe-coff, but maybe for elf, too) that NOLOAD
means to discard sections from linking?
Cheers,
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
next prev parent reply other threads:[~2010-10-16 20:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 0:03 Alan Modra
2010-10-15 20:31 ` Dave Korn
2010-10-15 20:36 ` Kai Tietz
2010-10-15 22:27 ` Dave Korn
2010-10-15 22:28 ` Dave Korn
2010-10-16 2:36 ` Alan Modra
2010-10-16 20:08 ` Kai Tietz [this message]
2010-10-16 20:19 ` Dave Korn
2010-10-17 10:32 ` Kai Tietz
2010-10-17 16:40 ` Dave Korn
2010-10-17 19:18 ` Kai Tietz
2010-10-17 23:29 ` Alan Modra
2010-10-18 6:22 ` Kai Tietz
2010-10-18 13:44 ` Alan Modra
2010-10-18 14:39 ` Kai Tietz
2010-10-19 15:05 ` Kai Tietz
2010-10-20 14:48 ` Dave Korn
2010-10-26 12:46 ` Alan Modra
2010-10-26 16:56 ` Dave Korn
2010-11-05 4:36 ` Dave Korn
2010-11-05 5:58 ` Alan Modra
2010-11-05 7:24 ` Dave Korn
2010-10-21 23:32 ` Alan Modra
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='AANLkTima-b18poWw=8RSP3-dT=2Vt2T4FhMd5oGH3OTr@mail.gmail.com' \
--to=ktietz70@googlemail.com \
--cc=binutils@sourceware.org \
--cc=dave.korn.cygwin@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).