This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH,RFC] collect2 LTO for AIX
- From: Martin Liška <mliska at suse dot cz>
- To: David Edelsohn <dje dot gcc at gmail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 4 Jul 2019 16:38:14 +0200
- Subject: Re: [PATCH,RFC] collect2 LTO for AIX
- References: <CAGWvnymeyvkoqoxnjvQGhTv3UfVgpPW3wpuFW2-gUtt0krSAemail@example.com>
Recently I've introduced a new .gnu.lto_.lto section that
is supposed to provide meta information about a LTO bytecode.
As a further step, I'm planning to teach binutils about
existence of the section and I'll remove in the future
emission of __gnu_lto_slim and __gnu_lto_v1 symbols.
The former one is used by binutils to identify if
an object is a slim LTO object. The later one is currently
used only in gcc/collect2.c and was added by David's patch.
My question is: Can we remove __gnu_lto_v1 right now and
XCOFF will use something similar to ELF (has_lto_section)?
Can you David help me with that please?