Re: Clean up LTO generation

2013-11-18 Thread Richard Biener
On Mon, Nov 18, 2013 at 2:19 PM, Bernd Schmidt wrote: > On 11/18/2013 02:03 PM, Jan Hubicka wrote: >>> On Mon, Nov 18, 2013 at 11:10 AM, Bernd Schmidt >>> wrote: The following patch simplifies this by getting rid of all_lto_gen_passes. We could simplify a little further if we decided w

Re: Clean up LTO generation

2013-11-18 Thread Bernd Schmidt
On 11/18/2013 02:03 PM, Jan Hubicka wrote: >> On Mon, Nov 18, 2013 at 11:10 AM, Bernd Schmidt >> wrote: >>> The following patch simplifies this by getting rid of >>> all_lto_gen_passes. We could simplify a little further if we decided we >>> really don't need two different timevars for different

Re: Clean up LTO generation

2013-11-18 Thread Jan Hubicka
> On Mon, Nov 18, 2013 at 11:10 AM, Bernd Schmidt > wrote: > > I'm looking into using LTO to pass information between compilers for > > different targets, for the OpenACC implementation. This area of the > > compiler seems somewhat obfuscated by overengineering, and I'd like to > > simplify it fi

Re: Clean up LTO generation

2013-11-18 Thread Richard Biener
On Mon, Nov 18, 2013 at 11:10 AM, Bernd Schmidt wrote: > I'm looking into using LTO to pass information between compilers for > different targets, for the OpenACC implementation. This area of the > compiler seems somewhat obfuscated by overengineering, and I'd like to > simplify it first to make i

Clean up LTO generation

2013-11-18 Thread Bernd Schmidt
I'm looking into using LTO to pass information between compilers for different targets, for the OpenACC implementation. This area of the compiler seems somewhat obfuscated by overengineering, and I'd like to simplify it first to make it easier to work with. lto_gimple_out and lto_finish_out aren't