From: Alan Modra <amodra@gmail.com>
To: Oleg Tolmatcev <oleg.tolmatcev@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] optimize handle_COMDAT
Date: Wed, 26 Apr 2023 15:29:49 +0930 [thread overview]
Message-ID: <ZEi91e/BbLW7A9mW@squeak.grove.modra.org> (raw)
In-Reply-To: <CACcXsZjbOetUzc5MOhWFJbqkkhuurqcDD7faHs9PJjM02Be9TA@mail.gmail.com>
On Tue, Apr 25, 2023 at 06:48:11PM +0200, Oleg Tolmatcev via Binutils wrote:
> Hello all,
>
> linking with ld on Windows is currently slow. RPCS3 with BUILD_LLVM=ON
> takes 9 minutes to link on my PC and I am talking about the last step
> only. I have profiled `ld` with a profiler and optimized the code.
> With all the patches the linking only takes 1 min. now.
>
> This is the first patch of the series of 4 patches. Should I submit
> all at once or wait until this one is accepted before I send the next
> one?
Best get this one accepted first, because it has problems.
> diff --git a/bfd/bfd-in2.h b/bfd/bfd-in2.h
You shouldn't be editing bfd-in2.h. It is a generated file, your
changes will disappear.
> @@ -6822,6 +6822,15 @@ struct bfd
>
> /* For input BFDs, the build ID, if the object has one. */
> const struct bfd_build_id *build_id;
> + htab_t flags_hash;
> +};
Also, since flags_hash is specific to PE, it doesn't belong in
struct bfd. I think it should instead be put into struct pe_tdata,
see libcoff-in.h.
> diff --git a/bfd/opncls.c b/bfd/opncls.c
Your opncls.c changes don't belong there either. Likely peicode.h is
the correct place.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2023-04-26 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 16:48 Oleg Tolmatcev
2023-04-26 5:59 ` Alan Modra [this message]
2023-04-29 12:39 ` Oleg Tolmatcev
2023-05-04 4:11 ` Alan Modra
2023-05-04 17:33 ` Oleg Tolmatcev
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=ZEi91e/BbLW7A9mW@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=oleg.tolmatcev@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).