This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Update LTO plugin interface
- From: Ian Lance Taylor <iant at google dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: GCC Development <gcc at gcc dot gnu dot org>, Binutils <binutils at sourceware dot org>
- Date: Wed, 01 Dec 2010 10:54:03 -0800
- Subject: Re: Update LTO plugin interface
- References: <AANLkTi=KDAW7Gw6422SB7=bKS0NZYfNjeVDbGT7P5vAn@mail.gmail.com>
"H.J. Lu" <hjl.tools@gmail.com> writes:
> b. Compiler plugin controls what linker uses to generate the final executable:
> i. The linker command line order should be the same, with or without LTO.
> c. Add a cmdline bit field to
> struct ld_plugin_input_file
> {
> const char *name;
> int fd;
> off_t offset;
> off_t filesize;
> void *handle;
> unsigned int cmdline : 1;
> };
Just make it an int. But I don't see why this is needed. The plugin
already knows the files that it passed to add_input_file and
add_input_library. Why does it need to linker to report back where the
file came from? Why doesn't the plugin just keep track?
Ian