On 08/25/2015 02:54 PM, Steve Ellcey wrote:
> Actually, it looks like is peephole2 that is eliminating the
> instructions (and .cfi psuedo-ops).
> I am not entirely sure I need the code or if I just need the .cfi
> psuedo-ops and that I need the code to generate the .cfi stuff.
Don't create any ne
On 08/25/2015 03:54 PM, Steve Ellcey wrote:
On Tue, 2015-08-25 at 14:44 -0600, Jeff Law wrote:
I want to preserve the copy of $sp to $12 and I also want to preserve the
.cfi psuedo-ops (and code) in the exit block and epilogue in order for
exception handling to work correctly. One way I though
On Tue, 2015-08-25 at 14:44 -0600, Jeff Law wrote:
> > I want to preserve the copy of $sp to $12 and I also want to preserve the
> > .cfi psuedo-ops (and code) in the exit block and epilogue in order for
> > exception handling to work correctly. One way I thought of doing this
> > is to create an
On 08/25/2015 12:39 PM, Steve Ellcey wrote:
I have a question about FAKE, EH, and ABNORMAL edges. I am not sure I
understand all the implications of each type of edge from the description
in cfg-flags.def.
I am trying to implement dynamic stack alignment for MIPS and I have code
that does the
I have a question about FAKE, EH, and ABNORMAL edges. I am not sure I
understand all the implications of each type of edge from the description
in cfg-flags.def.
I am trying to implement dynamic stack alignment for MIPS and I have code
that does the following:
prologue
c
