Re: lto pseudo-object files and fixed registers

2012-02-07 Thread Andrew Pinski
On Tue, Feb 7, 2012 at 9:27 AM, Andi Kleen wrote: > Richard Guenther writes: >> >> You then can do >> >>  gcc $OPTIONS -flto a.c -o a.o >>  gcc $OPTIONS -flto b.c -o b.o >>  gcc $OPTIONS -ffixed-r9 -ffixed-r10 -flto d.c -o d.o >>  gcc $OPTIONS -ffixed-r9 -ffixed-r10 -flto e.c -o e.o >>  gcc $OPTI

Re: lto pseudo-object files and fixed registers

2012-02-07 Thread Andi Kleen
Richard Guenther writes: > > You then can do > > gcc $OPTIONS -flto a.c -o a.o > gcc $OPTIONS -flto b.c -o b.o > gcc $OPTIONS -ffixed-r9 -ffixed-r10 -flto d.c -o d.o > gcc $OPTIONS -ffixed-r9 -ffixed-r10 -flto e.c -o e.o > gcc $OPTIONS -flto a.o b.o -o non-fixed-reg-part.o -r -nostdlib > gcc

Re: lto pseudo-object files and fixed registers

2012-02-07 Thread Konstantin Vladimirov
Hi, Thanks so much, this exactly solves issue. I didn't know about this option, it seems very useful in such cases. --- With best regards, Konstantin On Tue, Feb 7, 2012 at 5:11 PM, Richard Guenther wrote: > On Tue, Feb 7, 2012 at 1:57 PM, Konstantin Vladimirov > wrote: >> Hi, >> >> That is go

Re: lto pseudo-object files and fixed registers

2012-02-07 Thread Richard Guenther
On Tue, Feb 7, 2012 at 1:57 PM, Konstantin Vladimirov wrote: > Hi, > > That is good solution, thanks. > > But what if I want to compile e.o and d.o with cross-module inlining > (but also with fixed regs and so, without lto, as you are suggesting)? > On gcc-4.3.3, I had "combine" option for such ca

Re: lto pseudo-object files and fixed registers

2012-02-07 Thread Konstantin Vladimirov
Hi, That is good solution, thanks. But what if I want to compile e.o and d.o with cross-module inlining (but also with fixed regs and so, without lto, as you are suggesting)? On gcc-4.3.3, I had "combine" option for such cases. Is it completely impossible in gcc 4.6.2? --- With best regards, Kon

Re: lto pseudo-object files and fixed registers

2012-02-07 Thread Richard Guenther
On Tue, Feb 7, 2012 at 1:26 PM, Konstantin Vladimirov wrote: > Hi, > > Consider some project, consisting of files: a.c, b.c, d.c and e.c > > Compiler is gcc 4.6.2 > > Files a.c and b.c are performance bottlenecks and requires heavy > cross-module inline, so must be compiled with -flto option > Fil

lto pseudo-object files and fixed registers

2012-02-07 Thread Konstantin Vladimirov
Hi, Consider some project, consisting of files: a.c, b.c, d.c and e.c Compiler is gcc 4.6.2 Files a.c and b.c are performance bottlenecks and requires heavy cross-module inline, so must be compiled with -flto option Files d.c and e.c is preffered to be compiled with lto option too, but they are