On Tue, 25 Oct 2011, Joseph S. Myers wrote:
> On Tue, 25 Oct 2011, Richard Guenther wrote:
>
> > Joseph, does this look like a sensible use of the common
> > machinery? Do we want the init from COLLECT_GCC_OPTIONS
> > in opts-common.c instead?
>
> Certainly there should be a single function to
On Tue, 25 Oct 2011, Richard Guenther wrote:
> Joseph, does this look like a sensible use of the common
> machinery? Do we want the init from COLLECT_GCC_OPTIONS
> in opts-common.c instead?
Certainly there should be a single function to process COLLECT_GCC_OPTIONS
into an array of strings, even
On Tue, 25 Oct 2011, Richard Guenther wrote:
>
> This moves lto-wrapper over to use common option processing to
> parse and re-emit options from COLLECT_GCC_OPTIONS. In a second
> step I will move the merging/complaining about different options
> in different LTO input files to the LTO driver (w
This moves lto-wrapper over to use common option processing to
parse and re-emit options from COLLECT_GCC_OPTIONS. In a second
step I will move the merging/complaining about different options
in different LTO input files to the LTO driver (which is what
lto-wrapper is).
Bootstrap and regtest pen
