On Mon, 2009-08-10 at 15:09 +0200, Steven Bosscher wrote:
> On Mon, Aug 10, 2009 at 1:16 PM, Ramana
> Radhakrishnan wrote:
> > I wonder if the best way to fix this is to teach ifcvt.c to handle
> > conditional returns.
>
> Yes. This is a bug in the middle-end. I can only guess why you are
> the
On Mon, Aug 10, 2009 at 1:16 PM, Ramana
Radhakrishnan wrote:
> I wonder if the best way to fix this is to teach ifcvt.c to handle
> conditional returns.
Yes. This is a bug in the middle-end. I can only guess why you are
the first to run into this (the ia64 return instruction is not
predicable?) b
Hi,
While experimenting to see if some of the bits in the ARM backend which
do predicated execution can be removed in favour of the more generic
bits in ifcvt.c. I attempted to turn on conditional calls using the
predicable attribute on the ARM port.
I've run into an ICE in the ifcvt pass for th
On Sun, 29 May 2005, Steven Bosscher wrote:
> I don't understand what lines 2728 to 2741 are for. Could someone give
> an example of when we can have a then_bb that has no successors, but
> still ends in something that satisfies simplejump_p()? What kind of
> strange indirect jump would that be?
Hi,
ifcvt.c has this code in find_if_block():
2718/* If the THEN block has no successors, conditional execution can
still
2719 make a conditional call. Don't do this unless the ELSE block has
2720 only one incoming edge -- the CFG manipulation is too ugly
otherwise.
272
