Re: issue of store to stack after an instruction

2011-10-25 Thread Konrad Eisele
Eric Botcazou wrote: >> I just need to save it. It needs to be saved so that the FPU >> pipeline is flushed. > > Then why not save it just below the stack pointer? > Wow, yes, that seems the right way! How simple, Thanks.

Re: issue of store to stack after an instruction

2011-10-24 Thread Eric Botcazou
> I just need to save it. It needs to be saved so that the FPU > pipeline is flushed. Then why not save it just below the stack pointer? -- Eric Botcazou

Re: issue of store to stack after an instruction

2011-10-24 Thread Konrad Eisele
Eric Botcazou wrote: >> I would like to implement a compiler fix for a SPARC-cpu variant >> that does the following: >> After each "fdivs" (SPARC single-float division) save the destination >> FPU register to a stack memory location. > > Do you need to reload it afterward or just save it? > I

Re: issue of store to stack after an instruction

2011-10-24 Thread Eric Botcazou
> I would like to implement a compiler fix for a SPARC-cpu variant > that does the following: > After each "fdivs" (SPARC single-float division) save the destination > FPU register to a stack memory location. Do you need to reload it afterward or just save it? -- Eric Botcazou

issue of store to stack after an instruction

2011-10-24 Thread Konrad Eisele
Hello, I would like to implement a compiler fix for a SPARC-cpu variant that does the following: After each "fdivs" (SPARC single-float division) save the destination FPU register to a stack memory location. The sparc.md definition of fdivs is this one: (define_insn "divsf3" [(set (match_oper