This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [lto][patch] Use @args when calling lto-wrapper
- From: Ian Lance Taylor <iant at google dot com>
- To: Rafael Espindola <espindola at google dot com>
- Cc: Andrew Pinski <pinskia at gmail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 04 Feb 2009 07:40:15 -0800
- Subject: Re: [lto][patch] Use @args when calling lto-wrapper
- References: <38a0d8450901290457y547be78cgb108d26f8a5f1aa1@mail.gmail.com> <38a0d8450901290459n2ca61c6h1227ed4a55430bdf@mail.gmail.com> <de8d50360901291131v6e53a1dkbfe87579a22a0d97@mail.gmail.com> <38a0d8450902040719n1d936e6cmdbb42c360ceb6718@mail.gmail.com>
Rafael Espindola <espindola@google.com> writes:
>> Also lto-plugin should use the pex interface instead of fork/execv.
>
> What is the advantage for the simple case of just one subcommand? The plugin
> only works on ELF systems...
Plenty of people use Windows hosts to cross-compile code for embedded
systems using ELF. Those people should be permitted to use LTO.
In gcc and the binutils executing another program should always be
done via the pex routines. That's a flat rule, no exceptions allowed
without special pleading.
The pex routines are fairly easy to use. As a bonus, they will be
slightly more efficient since they will use vfork when available, they
will handle some temporary error cases, they will issue standard error
messages, etc.
Ian