Steve Ellcey writes:
> On Thu, 2015-08-13 at 02:14 -0700, Matthew Fortune wrote:
> > Hi Steve,
> >
> > Overall, I don't think these optimizations are ready to include. In
> > principle
> > the idea looks good but it is done at the wrong point in the compiler in my
> > opinion.
> >
> > The biggest
On Thu, 2015-08-13 at 02:14 -0700, Matthew Fortune wrote:
> Hi Steve,
>
> Overall, I don't think these optimizations are ready to include. In principle
> the idea looks good but it is done at the wrong point in the compiler in my
> opinion.
>
> The biggest concern I have is that the analysis shou
Hi Steve,
Overall, I don't think these optimizations are ready to include. In principle
the idea looks good but it is done at the wrong point in the compiler in my
opinion.
The biggest concern I have is that the analysis should be possible at (or
prior to) the point where the prologue/epilogue ar
On Fri, 2015-07-31 at 00:32 +, Joseph Myers wrote:
> New command-line options need documenting in invoke.texi.
Good point, thanks for catching that. Here is an updated patch with
invoke.texi. There are no other changes to the patch.
Steve Ellcey
sell...@imgtec.com
2015-07-31 Steve Ellce
New command-line options need documenting in invoke.texi.
--
Joseph S. Myers
jos...@codesourcery.com
This patch implements a MIPS o32 ABI specific optimization called frame
header optimization. In the o32 ABI, routines allocate 16 bytes on the
stack before calling another routine. This space is used by the callee
as space to write the register arguments to if their address is taken.
The n32 and
