On 3/22/07, Alexander Lamaison <[EMAIL PROTECTED]> wrote:
> > The tree_opt_pass for my pass has PROP_ssa set in the
> properties_required
> > field. Is this all I need to do?
>
> You need to put your pass after pass_build_ssa. Setting PROP_ssa does
> not build SSA itself, but it will cause an a
> > I think (if I'm correctly interpreting the list in passes.c) it is.
> It's
> > right after pass_warn_function_noreturn, just before pass_mudflap_2.
> Is
> > this right? I don't get any assertion about SSA not being available.
>
> In this case, it is also after pass_del_ssa, which means SSA ha
> I think (if I'm correctly interpreting the list in passes.c) it is. It's
> right after pass_warn_function_noreturn, just before pass_mudflap_2. Is
> this right? I don't get any assertion about SSA not being available.
In this case, it is also after pass_del_ssa, which means SSA has already
be
> > The tree_opt_pass for my pass has PROP_ssa set in the
> properties_required
> > field. Is this all I need to do?
>
> You need to put your pass after pass_build_ssa. Setting PROP_ssa does
> not build SSA itself, but it will cause an assertion failure if the
> pass is run while SSA is (not yet
> The tree_opt_pass for my pass has PROP_ssa set in the properties_required
> field. Is this all I need to do?
You need to put your pass after pass_build_ssa. Setting PROP_ssa does
not build SSA itself, but it will cause an assertion failure if the
pass is run while SSA is (not yet) available.
