This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] Remove flow_loop_scan


Hello,

> So what would be the procedure to get loop exit edges marked without
> having to run the entire loop optimizer?
> 
> The code to prevent the jump threader from creating irreducible regions
> needs this information so that it can determine if it is safe to thread
> through a block with an incoming back edge.

ifcvt.c:mark_loop_exit_edges could be exported (and free_dominance_info
call removed from it).

Long term, we would like to keep information about loops up-to-date for most
of optimizations, which would make EDGE_LOOP_EXIT unnecessary.

Zdenek


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]