From: "pro@helflym.eu" <pro@helflym.eu>
To: "Nick Clifton" <nickc@redhat.com>
Cc: "CHIGOT, CLEMENT" <clement.chigot@atos.net>,
"binutils@sourceware.org" <binutils@sourceware.org>,
"Kavana N Bhat" <Kavana.bhat@in.ibm.com>,
"Ayappan P2" <ayappap2@in.ibm.com>
Subject: Re: [PATCH 1/2] bfd: move the generation of the XCOFF .loader section after allocations
Date: Wed, 20 Apr 2022 11:50:23 +0200 [thread overview]
Message-ID: <10d3-625fd780-61-12f24c40@194966789> (raw)
In-Reply-To: <111426e6-d728-6fc1-facf-63a0a1953897@redhat.com>
Hi Nick,
Could you please apply it to me ? I'm no longer working for AIX, thus I don't have access to my setup anymore.
I might be able to do it later but not earlier than mid-May. Thus I would be grateful if you can do it for me.
Thanks,
Clément
On Wednesday, April 13, 2022 18:29 CEST, Nick Clifton <nickc@redhat.com> wrote:
Hi Clement,
> bfd/ChangeLog:
>
> * coff-rs6000.c (_bfd_xcoff_put_ldsymbol_name): Write len in
> ldinfo->strings instead of directly in the output_bfd.
> * coff64-rs6000.c (_bfd_xcoff64_put_ldsymbol_name): Likewise.
> * xcofflink.c (struct xcoff_link_hash_table): Remove ldrel_count
> field. Add ldinfo field.
> (xcoff_mark_symbol): Adjust to new ldinfo field.
> (xcoff_mark): Likewise.
> (bfd_xcoff_link_count_reloc): Likewise.
> (xcoff_build_loader_section): Split into two functions: one that
> build the loader section (this function) and one that only size
> it...
> (xcoff_size_loader_section): ... (this function).
> (bfd_xcoff_size_dynamic_sections): Adapt to new ldinfo field.
> Move the part where the dynamic sections are build to ...
> (bfd_xcoff_build_dynamic_sections): ... this function.
> * xcofflink.h: Add bfd_xcoff_build_dynamic_sections prototype.
>
> include/ChangeLog:
>
> * coff/xcoff.h (struct xcoff_loader_info): Add ldrel_count and
> libpath fields.
>
> ld/ChangeLog:
>
> * emultempl/aix.em (_after_allocation): New function.
Patch approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2022-04-20 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 15:01 CHIGOT, CLEMENT
2022-04-13 16:29 ` Nick Clifton
2022-04-20 9:50 ` pro [this message]
2022-04-20 14:10 ` Nick Clifton
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=10d3-625fd780-61-12f24c40@194966789 \
--to=pro@helflym.eu \
--cc=Kavana.bhat@in.ibm.com \
--cc=ayappap2@in.ibm.com \
--cc=binutils@sourceware.org \
--cc=clement.chigot@atos.net \
--cc=nickc@redhat.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).