From: Jan Beulich <jbeulich@suse.com>
To: Mark Harmstone <mark@harmstone.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH v2] ld: Sort section contributions in PDB files
Date: Mon, 27 Feb 2023 10:13:53 +0100 [thread overview]
Message-ID: <3aeaf40a-f59c-32be-9fad-1efc18ce6bcb@suse.com> (raw)
In-Reply-To: <20230227005935.12270-1-mark@harmstone.com>
On 27.02.2023 01:59, Mark Harmstone wrote:
> @@ -4177,32 +4210,43 @@ create_section_contrib_substream (bfd *abfd, void **data, uint32_t *size)
> {
> for (asection *s = in->sections; s; s = s->next)
> {
> - uint16_t sect_num;
> -
> if (s->size == 0 || discarded_section (s))
> continue;
>
> - sect_num = find_section_number (abfd, s->output_section);
> -
> - memcpy (&sc->characteristics,
> - sect_flags + ((sect_num - 1) * sizeof (uint32_t)),
> - sizeof (uint32_t));
> -
> - bfd_putl16 (sect_num, &sc->section);
> - bfd_putl16 (0, &sc->padding1);
> - bfd_putl32 (s->output_offset, &sc->offset);
> - bfd_putl32 (s->size, &sc->size);
> - bfd_putl16 (mod_index, &sc->module_index);
> - bfd_putl16 (0, &sc->padding2);
> - bfd_putl32 (0, &sc->data_crc);
> - bfd_putl32 (0, &sc->reloc_crc);
> + sc2->s = s;
> + sc2->sect_num = find_section_number (abfd, s->output_section);
> + sc2->mod_index = mod_index;
>
> - sc++;
> + sc2++;
> }
>
> mod_index++;
> }
>
> + qsort (sc_in, num_sc, sizeof (struct in_sc), section_contribs_compare);
You want to apply Nick's requested change here as well, changing
sizeof (struct in_sc) to sizeof (* sc_in). Okay with that adjustment,
assuming ...
> + ptr = *data;
> + sc = (struct section_contribution *) (ptr + 1); /* Skip the version word. */
... you did at least consider Nick's remark regarding this, but
didn't find any good replacement (and Nick's suggestion also didn't
fit).
Jan
next prev parent reply other threads:[~2023-02-27 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 0:59 Mark Harmstone
2023-02-27 9:13 ` Jan Beulich [this message]
2023-02-28 0:18 ` Mark Harmstone
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=3aeaf40a-f59c-32be-9fad-1efc18ce6bcb@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=mark@harmstone.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).